From: Benno Schulenberg Date: Sat, 18 Jul 2015 12:00:34 +0000 (+0000) Subject: Fixing a few typos and making some updates for 2.4.* in the FAQ. X-Git-Tag: v2.5.0~153 X-Git-Url: https://git.wh0rd.org/?a=commitdiff_plain;h=f1bd9588518bb843a8a8abe4b172b33c4828c79e;p=nano.git Fixing a few typos and making some updates for 2.4.* in the FAQ. git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@5309 35c25a1d-7b9e-4130-9fde-d3aeb78583b8 --- diff --git a/ChangeLog b/ChangeLog index f4297a46..3c1396cb 100644 --- a/ChangeLog +++ b/ChangeLog @@ -3,6 +3,7 @@ look for a new start only after an end, instead of right after the last start. This fixes bug #45525 and bug #41313 on Savannah. * src/nano.c, src/text.c, src/winio.c: Adjust some comments. + * doc/faq.html: Fix a few typos and make some updates for 2.4.*. 2015-07-17 Benno Schulenberg * src/files.c (open_buffer): Verify that a named and existing file diff --git a/doc/faq.html b/doc/faq.html index 7d94474d..5612bf05 100644 --- a/doc/faq.html +++ b/doc/faq.html @@ -28,8 +28,8 @@ 3.6. How can I make the executable smaller? This is too bloated!
3.7. Tell me more about this multibuffer stuff!
3.8. Tell me more about this verbatim input stuff!
- 3.9. How do I make a .nanorc file that nano will read when I start it?
- 3.9.1. How about in Win32?

+ 3.9a. How do I make a .nanorc file that nano will read when I start it?
+ 3.9b. How about in Win32?

4. Running

4.1. How do I open a file with a name beginning with '+' from the command line?
4.2. Ack! My Backspace/Delete/Enter/Meta/double bucky key doesn't seem to work! What can I do?
@@ -84,9 +84,9 @@

1.5. Why the name change from TIP?

On January 10, 2000, TIP was officially renamed to nano because of a namespace conflict with another program called 'tip'. The original 'tip' program "establishes a full duplex terminal connection to a remote host", and was included with many older Unix systems (and newer ones like Solaris). The conflict was not noticed at first because there is no 'tip' utility included with most GNU/Linux distributions (where nano was developed).

1.6. What is the current version of nano?

-

The current stable version of nano *should* be 2.2.6. Of course, you should always check the nano homepage to see what the latest and greatest version is.

+

The current stable version of nano *should* be 2.4.2. Of course, you should always check the nano homepage to see what the latest and greatest version is.

1.7. I want to read the man page without having to download the program!

-

Jeez, demanding, aren't we? Okay, look here.

+

Jeez, demanding, aren't we? Okay, look here.

2. Where to get GNU nano.

2.1. FTP and WWW sites that carry nano.

@@ -156,12 +156,12 @@

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.

Alternatively, if you've enabled Unicode support (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 instead. The prompt will change to "Unicode Input" when you do this.

-

3.9. 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 not have been compiled with --disable-nanorc, and must be version 1.1.12 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 nowrap" or "set suspend".

-

3.9. How about in Win32?

-

If you're using the official nano .zip file and have extracted all the files, you should take the file nano.rc and place it somewhere on your Win32 system (for example if you have write permission to do so, at the top of C:\). Then you must create an Environment variable called HOME which points to the directory where you put nano.rc. In Windows XP, you can get to Environment variables by right-clicking "My Computer" either on the desktop or in the Start Menu, and selecting Properties. This should bring up the System Properties panel. Then click the Advanced Tab, and there should be a button called Environment Variables. Click that to bring up the Environment Variables section. Now, under User Variables you should be able to click the New button, and make a new Variables Name called HOME, with the Variable Value of whatever path you copied nano.rc into (just the directory name; don't add nano.rc onto the end).

-

We're still working on documentation for enabling synax highlighting on Win32; please bear with us.

-

Note that the nano.rc file must remain Unix-formated in order for nano to understand it. In other words, you should probably use only nano to edit its config file. Other programs like Wordpad and Notepad will convert the file to DOS format when saving, and the latter does not even properly read Unix-formatted files to begin with.

+

3.9a. 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 not have been compiled with --disable-nanorc, and must be version 1.1.12 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 words set and unset plus the long option name for the feature. For example, "set nowrap" or "set smarthome".

+

3.9b. How about in Win32?

+

If you're using the official nano .zip file and have extracted all the files, you should take the file nano.rc and place it somewhere on your Win32 system (for example, if you have write permission to do so, at the top of C:\). Then you must create an Environment variable called HOME which points to the directory where you put nano.rc. In Windows XP, you can get to Environment variables by right-clicking "My Computer" either on the desktop or in the Start Menu, and selecting Properties. This should bring up the System Properties panel. Then click the Advanced Tab, and there should be a button called Environment Variables. Click that to bring up the Environment Variables section. Now, under User Variables you should be able to click the New button, and make a new Variables Name called HOME, with the Variable Value of whatever path you copied nano.rc into (just the directory name; don't add nano.rc onto the end).

+

We're still working on documentation for enabling syntax highlighting on Win32; please bear with us.

+

Note that the nano.rc file must remain Unix-formatted in order for nano to understand it. In other words, you should probably use only nano to edit its config file. Other programs like Wordpad and Notepad will convert the file to DOS format when saving, and the latter does not even properly read Unix-formatted files to begin with.

4. Running

4.1. How do I open a file with a name beginning with '+' from the command line?

@@ -184,7 +184,7 @@

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 database 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 a newer version (at least 0.9.9, but 2.2.6 is recommended).

+

Older versions of nano had this problem, please upgrade to a newer version (at least 0.9.9, but 2.4.2 is recommended).

4.8. [version 1.3.12 and later] I'm using glibc 2.2.3, and nano crashes when I use color support or do regular expression searches. How can I fix that?

It's a bug in glibc 2.2.3. You should upgrade to at least glibc 2.2.4.

4.9. [version 1.1.12 and earlier] Why does nano show ^\ in the shortcut list instead of ^J?

@@ -207,15 +207,15 @@

my_hdr X-Composer: nano x.y.z

Again, replace x.y.z with the version of nano you use.

4.12. 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.9.

+

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.

4.13. How do I select text for or paste text from the clipboard in an X terminal when I'm running nano in one and nano's mouse support is turned on?

Try holding down the Shift key and selecting or pasting the text as you normally would.

4.14. 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.15. On startup I get a message that says "Detected a legacy nano history file". Now older nano versions can't find my search history!

In nano 2.3.0, cursor-position history was introduced, and both history files now reside under a .nano directory in your home. nano was trying to move this file into the new location so it could continue to use it. This means that if you try and use an earlier version of nano, it will be unable to see your current search history. To fix this, run the following commands:
-mv ~/.nano/search_history ~/.nano_history
-ln -sf ~/.nano_history ~/.nano/search_history
+

mv ~/.nano/search_history ~/.nano_history
+ ln -sf ~/.nano_history ~/.nano/search_history

5. Internationalization

@@ -256,7 +256,9 @@ Of course, due to the license change you can now use the 7.5. Can I have write access to the subversion tree?

Re-read Section 7.4 and you should know the answer.

8. ChangeLog

-

2014/04/24 - A bunch of small fixes and updates. (Benno)
+

+2015/07/18 - More small fixes and updates. (Benno)
+2014/04/24 - A bunch of small fixes and updates. (Benno)
2009/11/30 - Update various bits for nano 2.2.x. (DLR)
2009/11/18 - Typo fix. (j.mader@gmail.com)
2008/03/16 - Update docs to refer to subversion instead of CVS, add more words about Alpine, and refer to Savannah for bugs and patches. (chrisa)