There's also the --enable-tiny option which disables everything above, as well as some larger chunks of the program (like the marker code that you use Control-^ to select with). Also, if you know you aren't going to be using other languages you can use --disable-nls to 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, on the other hand, you can't live without bells and whistles, you could try:
- --enable-extra Enable extra functions, including easter eggs
+ --enable-extra Enable extra features, currently only easter eggs
--enable-nanorc Enable use of .nanorc file
--enable-color Enable color and syntax highlighting
--enable-multibuffer Enable having multiple file buffers open
@@ -163,7 +163,7 @@
Turn off wrapping of text by default when the
user is root
To use multiple file buffers, you must be using nano 1.1.0 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.
+To use multiple file buffers, you must be using nano 1.1.0 or newer, and you must have configured nano with --enable-multibuffer (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.
3.8. Tell me more about this verbatim input stuff!
To use verbatim input, you must be using nano 1.3.1 or newer. 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".) Then press the key(s) that generate the character you want.
@@ -250,8 +250,9 @@8. ChangeLog
-2005/06/13 - Minor capitalization and wording fixes. (DLR) -2005/06/08 - Updated section 1.1 to mention the current maintainer. (DLR) +2005/06/15 - Update description of --enable-extra, and add missing line breaks. (DLR)
+2005/06/13 - Minor capitalization and wording fixes. (DLR)
+2005/06/08 - Updated section 1.1 to mention the current maintainer. (DLR)
2005/03/09 - Added question about opening files with names beginning with '+'s, and added a few more miscellaneous cosmetic fixes. (DLR)
2005/01/03 - Removed now-inaccurate note about verbatim input's not working at prompts, and update its description to mention that it handles hexadecimal values now. (DLR)
2004/11/21 - Listed sh as an example of a Bourne shell. (DLR)
diff --git a/doc/nanorc.sample b/doc/nanorc.sample index 76b6d4c4..d81eaf42 100644 --- a/doc/nanorc.sample +++ b/doc/nanorc.sample @@ -47,7 +47,7 @@ ## Allow multiple file buffers (inserting a file will put it into a ## separate buffer). You must have configured with --enable-multibuffer -## or --enable-extra for this to work. +## for this to work. ## # set multibuffer