From: David Lawrence Ramsey Date: Sun, 4 Jun 2006 17:22:16 +0000 (+0000) Subject: in faq.html, add minor punctuation and wording fixes X-Git-Tag: v1.3.12~59 X-Git-Url: https://git.wh0rd.org/?a=commitdiff_plain;h=7d9e5bfb369f8b6ef69b82fa4251d4d00aef4b58;p=nano.git in faq.html, add minor punctuation and wording fixes git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3621 35c25a1d-7b9e-4130-9fde-d3aeb78583b8 --- diff --git a/ChangeLog b/ChangeLog index 3709bba8..9786f1d6 100644 --- a/ChangeLog +++ b/ChangeLog @@ -396,6 +396,7 @@ CVS code - - Update section 3.8 to mention the new "Unicode Input" prompt, and how Unicode input only works when Unicode support is enabled. (DLR) + - Add minor punctuation and wording fixes. (DLR) - doc/nano.1: - Update the copyright years to include 2006. (DLR) - Explicitly mention that all regexes should be extended regular diff --git a/doc/faq.html b/doc/faq.html index 263ee04f..350a7af3 100644 --- a/doc/faq.html +++ b/doc/faq.html @@ -198,14 +198,14 @@

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

+

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

setenv EDITOR /usr/local/bin/nano

Change /usr/local/bin/nano to wherever nano is installed on your system. Type "which nano" to find out. This will not take effect until the next time you login. So log out and back in again.

-

Then on top that if you use Pine you must go into setup (type S at the main menu), then configure (type C). Hit enter on the lines that say:

+

Then, on top of that, if you use Pine, you must go into setup (type S at the main menu), and then configure (type C). Hit Enter on the lines that say:

[ ] enable-alternate-editor-cmd
[ ] enable-alternate-editor-implicitly

Then exit (E) and select Yes (Y).

-

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:

+

If you're a mutt user, you 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.12. I've compiled nano with color support, but I don't see any color when I run it!

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

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

8. ChangeLog

-

2006/05/27 - Update section 3.8 to mention the new "Unicode Input" prompt, and how Unicode input only works when Unicode support is enabled. (DLR)
+

2006/06/04 - Add minor punctuation and wording fixes. (DLR)
+2006/05/27 - Update section 3.8 to mention the new "Unicode Input" prompt, and how Unicode input only works when Unicode support is enabled. (DLR)
2006/05/12 - Remove section 4.4, and move all section 4 entries after it up one number, since it no longer applies. Meta-] and Meta-[ are no longer used to indent and unindent marked text, since they require that the bracket matching key change to Ctrl-], which is used as the telnet escape key (found by Chris). Also, make the link to the nano CVS page a bit more readable. (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)