From: David Lawrence Ramsey Date: Mon, 8 May 2006 14:12:36 +0000 (+0000) Subject: per Benno Schulenberg's patch (with a few tweaks by me), add a new X-Git-Tag: v1.3.12~198 X-Git-Url: https://git.wh0rd.org/?a=commitdiff_plain;h=27d5be5e36b4cefe9255012b654019a1cc83cfa9;p=nano.git per Benno Schulenberg's patch (with a few tweaks by me), add a new section 4.5, and move all section 4 entries after it down one number, to explain a problem that can occur when holding down keys to generate Meta sequences; also add a few more capitalization and wording fixes git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3482 35c25a1d-7b9e-4130-9fde-d3aeb78583b8 --- diff --git a/ChangeLog b/ChangeLog index e8f1a431..0bbca061 100644 --- a/ChangeLog +++ b/ChangeLog @@ -204,6 +204,10 @@ CVS code - - Add a new section 4.4, and move all section 4 entries after it down one number, to explain how to deal with problems typing Meta-[. (DLR) + - Add a new section 4.5, and move all section 4 entries after it + down one number, to explain a problem that can occur when + holding down keys to generate Meta sequences. (Benno + Schulenberg, minor tweaks by DLR) - Add a few capitalization and wording fixes. (DLR) - doc/nano.1, doc/nanorc.5, doc/rnano.1, doc/nano.texi: - Update the copyright years to include 2006. (DLR) diff --git a/doc/faq.html b/doc/faq.html index b7cd5370..f4f24ed3 100644 --- a/doc/faq.html +++ b/doc/faq.html @@ -32,18 +32,19 @@ 3.9. How do I make a .nanorc file that nano will read when I start it?

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/double bucky/meta key doesn't seem to work! What can I do?
+ 4.2. Ack! My Backspace/Delete/Enter/Meta/double bucky key doesn't seem to work! What can I do?
4.3. Ack! My numeric keypad's keys don't work properly when NumLock is off! What can I do?
4.4. Ack! When I press Meta-[ to unindent marked text, it only works after a short delay, and if I press Meta-[ again during the delay, I get a typed [ instead of another unindent. What gives?
- 4.5. How do I type the F13-F16 keys shown in the help browser? My keyboard only has F1-F12!
- 4.6. Nano crashes when I type <insert keystroke here>!
- 4.7. Nano crashes when I resize my window. How can I fix that?
- 4.8. [version 1.1.12 and earlier] Why does nano show ^\ in the shortcut list instead of ^J?
- 4.9a. [version 1.1.12 and earlier] When I type in a search string, the string I last searched for is already in front of my cursor! What happened?!
- 4.9b. [version 1.1.99pre1 and later] Hey, the search string behavior has reverted, it's now like Pico, what happened to the consistency?
- 4.10. How do I make nano my default editor (in Pine, mutt, etc.)?
- 4.11. I've compiled nano with color support, but I don't see any color when I run it!
- 4.12. How do I select text for the clipboard in an X terminal when I'm running nano in one and nano's mouse support is turned on?

+ 4.5. 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?
+ 4.6. How do I type the F13-F16 keys shown in the help browser? My keyboard only has F1-F12!
+ 4.7. Nano crashes when I type <insert keystroke here>!
+ 4.8. Nano crashes when I resize my window. How can I fix that?
+ 4.9. [version 1.1.12 and earlier] Why does nano show ^\ in the shortcut list instead of ^J?
+ 4.10a. [version 1.1.12 and earlier] When I type in a search string, the string I last searched for is already in front of my cursor! What happened?!
+ 4.10b. [version 1.1.99pre1 and later] Hey, the search string behavior has reverted, it's now like Pico, what happened to the consistency?
+ 4.11. How do I make nano my default editor (in Pine, mutt, etc.)?
+ 4.12. I've compiled nano with color support, but I don't see any color when I run it!
+ 4.13. How do I select text for the clipboard in an X terminal when I'm running nano in one and nano's mouse support is turned on?

5. Internationalization

5.1. There's no translation for my language!
5.2. I don't like the translation for <x> in my language. How can I fix it?
@@ -175,7 +176,7 @@

To open '+filename.txt' starting on line 1: nano +filename.txt
To open '+filename.txt' starting on line 10: nano +10 +filename.txt
To open '+filename.txt' starting on line 1 and 'filename.txt' starting on line 10 (if nano has been compiled with multibuffer support): nano +1 +filename.txt +20 filename.txt

-

4.2. Ack! My Backspace/Delete/Enter/double bucky/meta key doesn't seem to work! What can I do?

+

4.2. Ack! My Backspace/Delete/Enter/Meta/double bucky key doesn't seem to work! What can I do?

Try setting your $TERM variable to 'vt100'. Nano doesn't yet support every term entry under the sun.

Bourne shell users (bash and sh): export TERM=vt100
C Shell users (tcsh and csh): setenv TERM vt100

@@ -183,19 +184,21 @@

You can use the -K or --rebindkeypad options 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 press Meta-[ to unindent marked text, it only works after a short delay, and if I press Meta-[ again during the delay, I get a typed [ instead of another unindent. What gives?

This is a special case. Meta-[ followed by (for example) A through D corresponds to the arrow keys on many terminals, and the delay is needed in order to handle them. If you don't want to wait at all between unindents, you can hold down the Shift key when pressing Meta-[ to get Meta-{, which will do the same thing as Meta-[ without the delay.

-

4.5. How do I type the F13-F16 keys shown in the help browser? My keyboard only has F1-F12!

+

4.5. 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 is a bug in the terminal, not in nano. When a key is repeating faster than nano can process it, the keyboard buffer becomes full and starts dropping incoming keystrokes. Unfortunately, it doesn't just drop whole keystrokes; it can also drop parts of multibyte key combinations, resulting in nano's receiving a wrong key.

+

4.6. How do I type the F13-F16 keys shown in the help browser? 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>!

+

4.7. 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 to nano@nano-editor.org.

-

4.7. Nano crashes when I resize my window. How can I fix that?

+

4.8. 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 would be great, 0.9.12 is recommended).

-

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

+

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

The help (^G) and justify (^J) function were among the last to be written. To show the improvements that nano had over Pico (go to line # and replace), ^_ and ^\ were put on the shortcut list. Later, ^G came back in place of ^_ as it proved to be very valuable for new Unix users. If you use the -p option to nano (or hit Meta-P) you will get the same shortcuts at the bottom as Pico.

-

4.9a. [version 1.1.12 and earlier] When I type in a search string, the string I last searched for is already in front of my cursor! What happened?!

+

4.10a. [version 1.1.12 and earlier] When I type in a search string, the string I last searched for is already in front of my cursor! What happened?!

In nano version 0.9.20, the default is to have a completely consistent user interface across all user input functions. This means that regardless of whether you're being asked for a filename to insert or write, or a string to search for, the previous value is already inserted before the cursor. If you prefer the old behavior, use the Pico emulation mode (-p or --pico) or just hit Meta-P while in nano (see the ^G help text for more details).

-

4.9b. [version 1.1.99pre1 and later] Hey, the search string behavior has reverted, it's now like Pico, what happened to the consistency?

+

4.10b. [version 1.1.99pre1 and later] Hey, the search string behavior has reverted, it's now like Pico, what happened to the consistency?

It was decided that consistency was nice, but people are used to Pico's inconsistent behavior. Also, in version 1.1.99pre1, search and replace history was introduced. If you wish to edit your previous search/replace entry (or any previous entry), you can do so by hitting the up arrow to cycle through your history. This method allows the best of both worlds: You don't need to erase the previous string if you want to enter a new one, but you can with one keystroke recall previous entries for editing. Therefore there is now no "Pico mode", nano is and has always been a Pico clone, and clones by default should be compatible.

-

4.10. How do I make nano my default editor (in Pine, mutt, etc.)?

+

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

or if you use tcsh put this in your .cshrc file:

@@ -208,9 +211,9 @@

Mutt users should see an effect immediately the next time you log in, no further configuration is needed. However, if you want to let people know you use nano to compose your email messages, you can put a line like this in your .muttrc:

my_hdr X-Composer: nano x.y.z

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

-

4.11. I've compiled nano with color support, but I don't see any color when I run it!

+

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. Some example configurations are in the nanorc.sample that comes with the nano source or your nano package. See Section 3.9.

-

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

+

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.

5. Internationalization

@@ -253,7 +256,8 @@

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

8. ChangeLog

-

2006/05/01 - Add a new section 4.4, and move all section 4 entries after it down one number, to explain how to deal with problems typing Meta-[. Also add a few capitalization and wording fixes. (DLR)
+

2006/05/08 - Add a new section 4.5, and move all section 4 entries after it down one number, to explain a problem that can occur when holding down keys to generate Meta sequences. Also add a few more capitalization and wording fixes. (Benno Schulenberg, minor tweaks by DLR)
+2006/05/01 - Add a new section 4.4, and move all section 4 entries after it down one number, to explain how to deal with problems typing Meta-[. Also add a few capitalization and wording fixes. (DLR)
2006/04/14 - Clarify section 1.4: help menu -> help text display. (DLR, suggested by Benno Schulenberg)
2006/03/16 - Update the Free Translation Project's address, change the character set to UTF-8, and remove broken links to contributed RedHat nano packages. (DLR)
2005/11/21 - Clarify section 5.3 to better explain how to enable Unicode support, and remove the mention of quirks, since they turned out to not be a nano problem. (Mike Frysinger and DLR)