@@ -137,9 +137,9 @@
-Well, that's what the configure script defaults to. If you wish to change this, simply do this:
./configure --prefix=/usr
to put nano into /usr/bin when you run make install.
3.5. nano should automatically run strip on the binary when installing it!
+3.4. nano should automatically run strip on the binary when installing it!
-Actually, it does, but you have to use make install-strip. The default make install does not, and will not, run strip automatically.
3.6. How can I make the executable smaller? This is too bloated!
+3.5. How can I make the executable smaller? This is too bloated!
-Actually, there are several parts of the editor that can be disabled. You can pass arguments to the configure script that disable certain features. Here's a brief list:
--disable-browser Disable the built-in file browser @@ -161,13 +161,13 @@ --disable-wrapping Disable all hard-wrapping of textThere'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 with Control-^ to select text). 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 whether 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.
3.7. Tell me more about this multibuffer stuff!
+3.6. 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 after typing ^R. If you always want files to be loaded into their own buffers, use the -F or --multibuffer flag when you invoke nano, or add set multibuffer to your .nanorc file.
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 buffer open, the ^X shortcut will say "Close", instead of "Exit".
3.8. Tell me more about this verbatim input stuff!
+3.7. 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 status bar), then press the key(s) that generate the character you want.
Alternatively, if Unicode support is enabled (see section 5.3), you can press Meta-V and then type a six-digit hexadecimal code (from 000000 to 10FFFF, case-insensitive), and the character with the corresponding value will be inserted. The status bar will change to "Unicode Input: ......" when you do this.
3.9. How do I make a .nanorc file that will be read when I start nano?
+3.8. How do I make a .nanorc file that will be read when I start nano?
It's not hard at all! But, your nano must not have been compiled with --disable-nanorc. Then simply copy the sample.nanorc 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 of the file is simple. Flags are turned on and off by using the words set and unset plus the long option name for the feature. For example, "set nowrap" or "set smarthome".