From 14b0accd8115474078aa1ef9eb0d677140fd8bc3 Mon Sep 17 00:00:00 2001 From: Jordi Mallach Date: Tue, 2 Oct 2001 18:21:55 +0000 Subject: [PATCH] * We can't live WITHOUT bells and whistles 8) (Nathan Heagy) * Removed ftp.sourceforge.net from download sites as it'll go shortly. * Added the `testing' distribution page for nano in the Debian section. * Added a direct link to Debian's package pools too. * Added --disable-operatingdir to "how make nano smaller?". * Zsh advocacy :) git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@816 35c25a1d-7b9e-4130-9fde-d3aeb78583b8 --- faq.html | 51 ++++++++++++++++++++++++++++----------------------- 1 file changed, 28 insertions(+), 23 deletions(-) diff --git a/faq.html b/faq.html index e025ce0b..f1fdf82c 100644 --- a/faq.html +++ b/faq.html @@ -232,9 +232,6 @@ at the following fine web and ftp sites:
  • ftp://ftp.nano-editor.org/pub/nano
    • - -
  • -ftp://nano.sourceforge.net/pub/nano
    • @@ -252,9 +249,6 @@ packages.
  • ftp://ftp.nano-editor.org/pub/nano/RPMS
    • - -
  • -ftp://nano.sourceforge.net/pub/nano/RPMS
    • Additionally, check out the Redhat contribs section at: @@ -276,9 +270,15 @@ current nano packages for:
  • stable
    • +
  • +testing
    • +
  • unstable
    • +

    You can also have a look at the +Package Pool to see all the available binary and source packages.

    + Note that versions < 0.9.10 are probably not for those wanting to get serious work done, so if you are using Debian 2.2, check that you have updated to 2.2r3, which comes with nano 0.9.23. If you're @@ -372,6 +372,7 @@ list: --disable-browser Disables mini file browser --disable-wrapping Disables all wrapping of text (and -w flag) --disable-mouse Disables mouse support (and -m flag) +--disable-operatingdir Disable setting of operating directory
    There's also the --enable-tiny option which disables everything above, as well as some larger chunks of the program (like the marker code @@ -381,7 +382,7 @@ disable internationalization and save a few K to a few dozen K depending on if you have locale support on your system. And finally there's always good old strip to strip all debugging code and code that exists in libraries on your system. -

    If, in the other hand, you can't live with bells and whistles, you could +

    If, in the other hand, you can't live without bells and whistles, you could try: 

     --enable-extra          Enable extra functions, including easter eggs
@@ -394,29 +395,33 @@ try:
 
 3.7. Tell me more about this multibuffer stuff!
 
-
     To use multiple file buffers, you must be using nano 1.1.1
-or newer, and you must have configured nano with --enable-multibuffer or
---enable-extra (use nano -V to check).  Then when you want to enable inserting a file
-into its own buffer instead of into the current file, just hit Meta-F, then insert the
-file as normal with ^R.  If you always want files to be loaded into their own buffers,
+
     To use multiple file buffers, you must
+be using nano 1.1.1 or newer, and you must have configured nano with
+--enable-multibuffer or --enable-extra (use nano -V to check).
+Then when you want to enable inserting a file into its own buffer instead of
+into the current file, just hit Meta-F, then insert the file as normal
+with ^R.  If you always want files to be loaded into their own buffers,
 use the --multibuffer or -F flag when you invoke nano. 
    
 
-You can move between the buffers you have open with the Meta-< and Meta->
-keys, or more easily with Meta-, and Meta-. (clear as mud, right? =-).
-When you have more than one file buffer open, the ^X shortcut will say "Close", instead of the
-normal "Exit" when only one buffer is open. 
+You can move between the buffers you have open with the Meta-< and
+Meta-> keys, or more easily with Meta-, and Meta-.
+(clear as mud, right? =-). When you have more than one file buffer open,
+the ^X shortcut will say "Close", instead of the normal "Exit" when only one
+buffer is open. 
 
    
 
 
    
 
 3.8. How do I make a .nanorc file that nano will read when I start it?
    
 
-
     It's not hard at all!  But, your version of nano must have
-beem compiled with --enable-nanorc, and again must be version 1.1.1 or newer (use nano
--V to check your version and compiled features).  Then simply copy the nanorc.sample
-that came with the nano source or your nano package (most likely in /usr/doc/nano) to .nanorc
-in your home directory. If you didn't get one, the syntax is simple.  Flags are turned on and
-off by using the word set and the getopt_long flag for the feature, for example "set
+
     It's not hard at all!  But, your version
+of nano must have beem compiled with --enable-nanorc, and again must
+be version 1.1.1 or newer (use nano -V to check your version and compiled
+features).  Then simply copy the nanorc.sample
+that came with the nano source or your nano package (most likely in
+/usr/doc/nano) to .nanorc in your home directory. If you didn't get one,
+the syntax is simple.  Flags are turned on and off by using the word
+set and the getopt_long flag for the feature, for example "set
 pico" or "set nowrap". 
     
    
 
 
    4. Running
    
@@ -500,7 +505,7 @@ mutt, etc)?
 
 
    You need to make nano your $EDITOR.  If you want this
 to be saved, you should put a line like this in your .bashrc if
-you use bash:
+you use bash (or .zshrc if you believe in zsh):
 
    export EDITOR=/usr/local/bin/nano
 
    or if you use tcsh put this in your .cshrc file:
 
    setenv EDITOR /usr/local/bin/nano