diff --git a/doc/faq.html b/doc/faq.html index 3eba797d..0f3d4a07 100644 --- a/doc/faq.html +++ b/doc/faq.html @@ -36,6 +36,7 @@ 3.6. Tell me more about this multibuffer stuff!
3.7. Tell me more about this verbatim input stuff!
3.8. How do I make a .nanorc file that nano will read when I start it?
+ 3.9. Why does my self-compiled nano not read /etc/nanorc?

4. Running

@@ -169,6 +170,8 @@

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.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".

+

3.9. Why does my self-compiled nano not read /etc/nanorc?

+

By default (see 3.3), nano gets installed into /usr/local. This also means that at startup nano will read /usr/local/etc/nanorc instead of /etc/nanorc. You can make a symlink from the former to the latter if you want your self-compiled nano to read the same nanorc as the system-installed nano. Or you can configure your nano to overwrite the system nano (again, see 3.3).

4. Running