--disable-browser Disable the built-in file browser --disable-color Disable color and syntax highlighting + --disable-comment Disable the comment/uncomment function --disable-extra Disable extra features (currently only an easter egg) - --disable-help Disable help functions + --disable-help Disable the built-in help texts --disable-histories Disable the saving of search strings and cursor positions --disable-justify Disable justify/unjustify functions --disable-libmagic Disable the use of libmagic for determining a file's syntax + --disable-linenumbers Disable line numbering --disable-mouse Disable mouse support --disable-multibuffer Disable having multiple file buffers open --disable-nanorc Disable the use of .nanorc files @@ -155,7 +158,7 @@With --disable-wrapping-as-root you can disable any hard-wrapping by default when the user is root, useful to prevent accidentally changing long lines in system configuration files.
3.7. Tell me more about this multibuffer stuff!
-To use multiple file buffers, you must not have configured nano with --disable-multibuffer nor with --enable-tiny (use nano -V to check the compilation options). Then when you want to insert 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.
+To use multiple file buffers, you must not have configured nano with --disable-multibuffer nor with --enable-tiny (use nano -V to check the compilation options). Then when you want to insert a file into its own buffer instead of into the current file, just hit Meta-F after typing ^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 without holding Shift: 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. Tell me more about this verbatim input stuff!
When you want to insert a literal character into the file you're editing, such as a control character that nano usually treats as a command, first press Meta-V (if you're not at a prompt, you'll get the message "Verbatim Input" on the statusbar), then press the key(s) that generate the character you want.
@@ -184,16 +187,18 @@You can use the -K or --rebindkeypad option on the command line, or add the line set rebindkeypad to your .nanorc. However, nano's mouse support won't work properly if you do any of these things.
4.4. Ack! When I hold down a Meta key combination for a while, the character of the held key gets inserted now and then. What gives?
-This was a bug in how nano handled consecutive escape sequences. It should be fixed since version 2.6.0.
4.5. How do I type the F13-F16 keys shown in the help browser? My keyboard only has F1-F12!
+4.5. How do I type the F13-F16 keys listed in the help viewer? My keyboard only has F1-F12!
It depends on the terminal type you're using. On some terminals, such as the FreeBSD console, xterm, konsole, and gnome-terminal, Shift-F1 to Shift-F4 will generate F13 to F16. On other terminals, such as the Linux console, rxvt, and Eterm, Shift-F3 to Shift-F6 will generate F13 to F16.
4.6. nano crashes when I type <insert keystroke here>!
If you aren't trying some bizarre keystroke combination with some bizarre $TERM entry, chances are you have found a bug. You are welcome to submit it to the nano-devel list or in the bug tracker on Savannah.
4.7. nano crashes when I resize my window. How can I fix that?
-Older versions of nano had this problem. Please upgrade to version 2.7.0 or newer.
4.8. When I paste text into a document, each line gets indented further than the last. Why does nano do this, and how can I avoid it?
+4.8a. When I paste text into a document, each line gets indented further than the last. Why does nano do this, and how can I avoid it?
+You have the autoindent feature turned on. Hit Meta-I to turn it off, paste your text, and then hit Meta-I again to turn it back on.
4.8b. When I paste from Windows into a remote nano, nano rewraps the lines. What gives?
+When pasting from Windows, in some situations linefeeds are sent instead of carriage returns (Enters). And linefeeds are ^Js, which make nano justify (rewrap) the current paragraph. To prevent these linefeeds from causing these unwanted justifications, add this line to your .nanorc on the remote Linux box: unbind ^J main.
4.9. I've compiled nano with color support, but I don't see any color when I run it!
-+If you want nano to actually use color, you have to specify the color configurations you want it to use in your .nanorc. Several example configurations are in the doc/syntax subdirectory of the nano source, which are normally installed to /usr/local/share/nano. To enable all of them, uncomment the line # include "/usr/local/share/nano/*.nanorc" in your nanorc. See also section 3.9a.
If you want nano to actually use color, you have to specify the color configurations you want it to use in your .nanorc. Several example configurations are in the syntax/ subdirectory of the nano source, which are normally installed to /usr/local/share/nano. To enable all of them, uncomment the line # include "/usr/local/share/nano/*.nanorc" in your nanorc. See also section 3.9a.
4.10. How do I make nano my default editor (in Pine, 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 (or .zshrc if you believe in zsh):
export EDITOR=/usr/local/bin/nano
diff --git a/doc/nano.texi b/doc/nano.texi index b1596b98..47a35776 100644 --- a/doc/nano.texi +++ b/doc/nano.texi @@ -1480,12 +1480,16 @@ The possible options to @code{./configure} are: @table @code @item --disable-browser -Disable the mini file browser when reading or writing files. +Disable the mini file browser that can be called with ^T when reading +or writing files. @item --disable-color Disable support for the syntax coloring of files. This also eliminates the @code{-Y} command-line option, which chooses a specific syntax. +@item --disable-comment +Disable the single-keystroke comment/uncomment function (M-3). + @item --disable-extra Disable extra features. At the moment, this is just easter-egg-type stuff. @@ -1510,6 +1514,10 @@ Disable the use of the library of magic-number tests (for determining the file type and thus which syntax to use for colouring --- often the tests on filename extension and header line will be enough). +@item --disable-linenumbers +Disable the line-numbering function (M-#). This also eliminates the +@code{-l} command-line option, which turns line numbering on. + @item --disable-mouse Disable all mouse functionality. This also eliminates the @code{-m} command-line option, which enables the mouse functionality. @@ -1540,7 +1548,7 @@ command-line option, which allows specifying an alternate spell checker. Disable tab completion (when nano asks for a filename or a search string). @item --disable-wordcomp -Disable word completion. +Disable word completion (^[). @item --disable-wrapping Disable all hard-wrapping of overlong lines. This also eliminates the