From 93eb293fbb13f7a26020ea2391c8734dd57522be Mon Sep 17 00:00:00 2001 From: David Lawrence Ramsey Date: Fri, 5 Nov 2004 18:01:33 +0000 Subject: [PATCH] more faq updates: add questions about selecting text in an X terminal when mouse support is turned on and typing F13-F16 when the keyboard only has F1-F12, plus a few other miscellaneous bits git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2069 35c25a1d-7b9e-4130-9fde-d3aeb78583b8 --- ChangeLog | 5 ++++ doc/faq.html | 64 +++++++++++++++++++++++++++++----------------------- 2 files changed, 41 insertions(+), 28 deletions(-) diff --git a/ChangeLog b/ChangeLog index a08343e0..66145fea 100644 --- a/ChangeLog +++ b/ChangeLog @@ -366,6 +366,11 @@ CVS code - - faq.html: - Fixed inaccuracy: Pico compatibility mode was made the default in nano 1.1.99pre1, not 1.2.2. (DLR) + - Added question about how to type F13-F16 on terminals lacking + keys past F12 (suggested by Chris), question about how to + select text for the clipboard in X terminals with nano's mouse + support turned on (answer found by Joseph Birthisel), and + miscellaneous fixes and link updates. (DLR) - nano.1: - Eliminate references to the now removed -D/--dos and -M/--mac command line options. (DLR) diff --git a/doc/faq.html b/doc/faq.html index 7c4429a6..684d87e6 100644 --- a/doc/faq.html +++ b/doc/faq.html @@ -3,7 +3,6 @@ The GNU nano editor FAQ -

The nano FAQ

@@ -33,13 +32,15 @@ 3.9. How do I make a .nanorc file that nano will read when I start it?

4. Running

4.1. Ack! My backspace/delete/enter/double bucky/meta key doesn't seem to work! What can I do?
- 4.2. Nano crashes when I type <insert keystroke here>!
- 4.3. Nano crashes when I resize my window. How can I fix that?
- 4.4. [version 1.1.12 and earlier] Why does nano show ^\ in the shortcut list instead of ^J?
- 4.5a. [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.5b. [version 1.1.99pre1 and later] Hey, the search string behavior has reverted, it's now like Pico, what happened to the consistency?
- 4.6. How do I make nano my default editor (in Pine, mutt, etc.)?
- 4.7. I've compiled nano with color support, but I don't see any color when I run it!

+ 4.2. How do I type the F13-F16 keys shown in the help browser? My keyboard only has F1-F12!
+ 4.3. Nano crashes when I type <insert keystroke here>!
+ 4.4. Nano crashes when I resize my window. How can I fix that?
+ 4.5. [version 1.1.12 and earlier] Why does nano show ^\ in the shortcut list instead of ^J?
+ 4.6a. [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.6b. [version 1.1.99pre1 and later] Hey, the search string behavior has reverted, it's now like Pico, what happened to the consistency?
+ 4.7. How do I make nano my default editor (in Pine, mutt, etc.)?
+ 4.8. I've compiled nano with color support, but I don't see any color when I run it!
+ 4.9. 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?

@@ -80,7 +81,7 @@

1.6. What is the current version of nano?

The current version of nano *should* be 1.3.4. 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.

@@ -140,22 +141,26 @@

3.6. 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-tabcomp       Disables tab completion code for a smaller binary
+  --disable-tabcomp       Disable tab completion code for a smaller
+                          binary
   --disable-justify       Disable justify/unjustify function
-  --disable-speller       Disables spell checker function
-  --disable-help          Disables help function (^G)
-  --disable-browser       Disables mini file browser
-  --disable-wrapping      Disables all wrapping of text (and -w flag)
-  --disable-mouse         Disables mouse support (and -m flag)
+  --disable-speller       Disable spell checker function
+  --disable-help          Disable help function
+  --disable-browser       Disable mini file browser
+  --disable-wrapping      Disable all wrapping of text (and -w flag)
+  --disable-mouse         Disable mouse support (and -m flag)
   --disable-operatingdir  Disable setting of operating directory

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-nanorc         Enable use of .nanorc file
-  --enable-color          Enables color and syntax highlighting
-  --enable-multibuffer    Enables having multiple file buffers open
-  --enable-all            Enables all of the above features
+ --enable-color Enable color and syntax highlighting + --enable-multibuffer Enable having multiple file buffers open + --enable-all Enable all of the above features + --disable-wrapping-as-root + Turn off wrapping of text by default when the + user is root

3.7. Tell me more about this multibuffer stuff!

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.

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.

@@ -171,18 +176,19 @@

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

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

-

4.2. Nano crashes when I type <insert keystroke here>!

+

4.2. 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, or Eterm, Shift-F3 to Shift-F6 will generate F13 to F16.

+

4.3. 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.3. Nano crashes when I resize my window. How can I fix that?

+

4.4. 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.4. [version 1.1.12 and earlier] Why does nano show ^\ in the shortcut list instead of ^J?

+

4.5. [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.5a. [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.6a. [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.5b. [version 1.1.99pre1 and later] Hey, the search string behavior has reverted, it's now like Pico, what happened to the consistency?

+

4.6b. [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.6. How do I make nano my default editor (in Pine, mutt, etc.)?

+

4.7. 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:

@@ -195,8 +201,10 @@

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.7. I've compiled nano with color support, but I don't see any color when I run it!

+

4.8. 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.9. 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?

+

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

5. Internationalization

5.1. There's no translation for my language!

@@ -227,7 +235,7 @@ help-nano - http://mail.gnu.org/mailman/listinfo/help-nano/
nano-devel - http://mail.gnu.org/mailman/listinfo/nano-devel/

7.2. I want to send the development team a big load of cash (or just a thank you).

-

That's fine. Send it our way! Better yet, fix a bug in the program or implement a cool feature and send us that instead (though cash is fine too).

+

That's fine. Send it our way! Better yet, fix a bug in the program or implement a cool feature and send us that instead (though cash is fine too).

7.3. How do I submit a patch?

See Section 7.2.

7.4. How do I join the development team?

@@ -237,7 +245,7 @@

8. ChangeLog

-2004/11/05 - Fixed inaccuracy: Pico compatibility mode was made the default in nano 1.1.99pre1, not 1.2.2. (DLR) +2004/11/05 - Fixed inaccuracy: Pico compatibility mode was made the default in nano 1.1.99pre1, not 1.2.2. Also added question about how to type F13-F16 on terminals lacking keys past F12 (suggested by Chris), question about how to select text for the clipboard in X terminals with nano's mouse support turned on (answer found by Joseph Birthisel), and misc. fixes and link updates. (DLR)
2004/04/07 - Removed NumLock glitch question, as it's no longer needed. (DLR)
2004/01/30 - Fixed inaccuracy: multibuffer mode was first in nano 1.1.0, not 1.1.12. (DLR)
2003/12/31 - Added question about the new verbatim input function, and a few minor fixes. Removed reference to "set pico" (DLR).