From: David Lawrence Ramsey Date: Wed, 9 Mar 2005 22:53:11 +0000 (+0000) Subject: add faq entry about how to open files with names starting with '+'s X-Git-Tag: v1.3.6~62 X-Git-Url: https://git.wh0rd.org/?a=commitdiff_plain;h=256a8908aaccd753742912749de9c5170e8a4673;p=nano.git add faq entry about how to open files with names starting with '+'s git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2341 35c25a1d-7b9e-4130-9fde-d3aeb78583b8 --- diff --git a/ChangeLog b/ChangeLog index 00ce9ced..2766216d 100644 --- a/ChangeLog +++ b/ChangeLog @@ -306,6 +306,8 @@ CVS code - - Remove now-inaccurate note about verbatim input's not working at prompts, and update its description to mention that it handles hexadecimal values now. (DLR) + - Add question about opening files with names beginning with + '+'s, and add a few more miscellaneous cosmetic fixes. - nanorc.sample: - Add return to the "c-file" regexes. (DLR) - Clarify the text describing good values for whitespace diff --git a/doc/faq.html b/doc/faq.html index 906f6bd8..a526bd83 100644 --- a/doc/faq.html +++ b/doc/faq.html @@ -5,7 +5,7 @@ -

The nano FAQ

+

The GNU nano editor FAQ

Table of Contents

1. General

1.1 About this FAQ
@@ -24,23 +24,24 @@

3.1. How do I install the RPM or DEB package?
3.2. Compiling from source: WHAT THE HECK DO I DO NOW?
3.3. Why does everything go into /usr/local?
- 3.4. I get errors about 'bindtextdomain','gettext' and/or 'gettextdomain'. What can I do about it?
+ 3.4. I get errors about 'bindtextdomain','gettext', and/or 'gettextdomain'. What can I do about it?
3.5. Nano should automatically run strip on the binary when installing it!
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?

4. Running

-

4.1. Ack! My backspace/delete/enter/double bucky/meta key doesn't seem to work! What can I do?
- 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?

+

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

@@ -52,7 +53,7 @@ 6.5. Why doesn't UW simply change their license?
6.6. What if tomorrow UW changes the license to be truly Free Software?

7. Miscellaneous

-

7.1. Nano related mailing lists.
+

7.1. Nano-related mailing lists.
7.2. I want to send the development team a big load of cash (or just a thank you).
7.3. How do I submit a patch?
7.4. How do I join the development team?
@@ -134,7 +135,7 @@

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.4. I get errors about 'bindtextdomain', 'gettext' and/or 'gettextdomain'. What can I do about it?

+

3.4. I get errors about 'bindtextdomain', 'gettext', and/or 'gettextdomain'. What can I do about it?

Try doing a ./configure --with-included-gettext and see if that solves your problem. You may need to do a make clean; make to get it to work fully.

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

@@ -171,23 +172,26 @@

It's not hard at all! But, your version of nano must have been compiled with --enable-nanorc, and again 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".

4. Running

-

4.1. Ack! My backspace/delete/enter/double bucky/meta key doesn't seem to work! What can I do?

+

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

+

A command line option that begins with '+' is always treated as a starting line number. The option just after it, though, is always treated as a filename. So if you want to open '+filename.txt' starting on line 1, you should use:

+

nano +1 +filename.txt

+

4.2. Ack! My backspace/delete/enter/double bucky/meta 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

-

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

+

4.3. 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>!

+

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

+

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

+

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

+

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

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

+

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

+

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

@@ -228,7 +232,7 @@

Honestly nothing would make me happier than to see that happen. Nano would continue to be developed independently until such time as Pico had all the features nano did or the projects merged. That just does not seem very likely given that there has been no sign of any changes in the past few years in a positive direction.

7. Miscellaneous

-

7.1. Nano related mailing lists.

+

7.1. Nano-related mailing lists.

There are three mailing lists for nano hosted at Savannah, info-nano, help-nano and nano-devel. Info-nano is a very low traffic list where new versions of nano are announced (surprise!) Help-nano is for getting help with the editor without needing to hear all of the development issues surrounding it. Nano-devel is a normally low, sometimes high traffic list for discussing the present and future development of nano. Here are links to where you can sign up for a given list:

info-nano - http://mail.gnu.org/mailman/listinfo/info-nano/
help-nano - http://mail.gnu.org/mailman/listinfo/help-nano/
@@ -244,8 +248,9 @@

8. ChangeLog

-2005/01/03 - Remove now-inaccurate note about verbatim input's not working at prompts, and update its description to mention that it handles hexadecimal values now. (DLR) -2004/11/21 - List sh as an example of a Bourne shell. (DLR) +2005/03/09 - Added question about opening files with names beginning with '+'s, and added a few more miscellaneous cosmetic fixes. (DLR)
+2005/01/03 - Removed now-inaccurate note about verbatim input's not working at prompts, and update its description to mention that it handles hexadecimal values now. (DLR)
+2004/11/21 - Listed sh as an example of a Bourne shell. (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)