message. (DLR, found by Bill Marcum)
- doc/nano.1, doc/nanorc.5, doc/rnano.1, doc/nano.texi:
- Update the copyright years to include 2006. (DLR)
+ - Explicitly mention that all regexes should be extended regular
+ expressions. (DLR, suggested by John M. Gabriele)
+ - Miscellaneous minor fixes. (DLR)
- doc/nanorc.sample:
- Tweak the "c-file" regex for characters to accept '"' again,
as it's apparently valid, and simplify it. (DLR)
- Add sample regexes for Python. (singular on the Gentoo forums,
http://forums.gentoo.org/viewtopic.php?t=86562; minor tweaks
by DLR, suggested by John M. Gabriele)
+ - Explicitly mention that all regexes should be extended regular
+ expressions. (DLR, suggested by John M. Gabriele)
+- UPGRADE:
+ - Miscellaneous minor fixes. (DLR)
GNU nano 1.3.11 - 2006.03.30
- General:
.\" warranty.
.\"
.\" $Id$
-.TH NANORC 5 "version 1.3.11" "March 30, 2006"
+.TH NANORC 5 "version 1.3.11" "April 4, 2006"
.\" Please adjust this date whenever revising the manpage.
.\"
.SH NAME
\fI~/.nanorc\fP.
.SH OPTIONS
-The configuration file accepts a series of "set" and "unset" commands,
-which can be used to configure nano on startup without using the
-command-line options. Additionally, the "syntax", "color", and "icolor"
-keywords are used to define syntax highlighting rules for different text
-patterns. GNU nano will read one command per line.
+The configuration file accepts a series of \fBset\fP and \fBunset\fP
+commands, which can be used to configure nano on startup without using
+the command line options. Additionally, the \fBsyntax\fP, \fBcolor\fP,
+and \fBicolor\fP keywords are used to define syntax highlighting rules
+for different text patterns. GNU nano will read one command per line.
Options in rcfiles take precedence over nano's defaults, and command
line options override rcfile settings.
.TP
.B set quotestr "\fIstring\fP"
The email-quote string, used to justify email-quoted paragraphs. This
-is an "extended regular expression" if your system supports them,
+is an extended regular expression if your system supports them,
otherwise a literal string. The default value is
-"\fI^([\ \\t]*[#:>\\|}])+\fP" if you have regexps, or "\fI>\ \fP"
-otherwise. Note that '\\t' stands for a literal Tab character.
+"\fI^([\ \\t]*[#:>\\|}])+\fP" if you have extended regular expression
+support, or "\fI>\ \fP" otherwise. Note that '\\t' stands for a literal
+Tab character.
.TP
.B set/unset rebinddelete
Interpret the Delete key differently so that both Backspace and Delete
won't work properly with this option enabled.
.TP
.B set/unset regexp
-Do regular expression searches by default.
+Do extended regular expression searches by default.
.TP
.B set/unset smarthome
Make the Home key smarter. When Home is pressed anywhere but at the
.B syntax "\fIstr\fP" ["\fIfileregex\fP" ... ]
Defines a syntax named \fIstr\fP which can be activated via the \fB-Y\fP
flag, or will be automatically activated if the current filename matches
-\fIfileregex\fP. All following \fBcolor\fP and \fBicolor\fP statements
-will apply to \fIsyntax\fP until a new syntax is defined.
+the extended regular expression \fIfileregex\fP. All following
+\fBcolor\fP and \fBicolor\fP statements will apply to \fIsyntax\fP until
+a new syntax is defined.
The \fInone\fP syntax is reserved; specifying it on the command line is
the same as not having a syntax at all. The \fIdefault\fP syntax is
.TP
.B color \fIfgcolor\fP,\fIbgcolor\fP "\fIregex\fP" ...
For the currently defined syntax, display all expressions matching
-\fIregex\fP with foreground color \fIfgcolor\fP and background color
-\fIbgcolor\fP, at least one of which must be specified. Legal colors
-for foreground and background color are: white, black, red, blue, green,
-yellow, magenta, and cyan. You may use the prefix "bright" to force a
-stronger color highlight for the foreground. If your terminal supports
-transparency, not specifying a \fIbgcolor\fP tells \fBnano\fP to attempt
-to use a transparent background.
+the extended regular expression \fIregex\fP with foreground color
+\fIfgcolor\fP and background color \fIbgcolor\fP, at least one of which
+must be specified. Legal colors for foreground and background color
+are: white, black, red, blue, green, yellow, magenta, and cyan. You may
+use the prefix "bright" to force a stronger color highlight for the
+foreground. If your terminal supports transparency, not specifying a
+\fIbgcolor\fP tells \fBnano\fP to attempt to use a transparent
+background.
.TP
.B icolor \fIfgcolor\fP,\fIbgcolor\fP "\fIregex\fP" ...
Same as above, except that the expression matching is case insensitive.
.TP
.B color \fIfgcolor\fP,\fIbgcolor\fP start="\fIsr\fP" end="\fIer\fP"
-Display expressions which start with \fIsr\fP and end with \fIer\fP
-with foreground color \fIfgcolor\fP and background color \fIbgcolor\fP,
+Display expressions which start with the extended regular expression
+\fIsr\fP and end with the extended regular expression \fIer\fP with
+foreground color \fIfgcolor\fP and background color \fIbgcolor\fP,
at least one of which must be specified. This allows syntax
highlighting to span multiple lines. Note that all subsequent instances
of \fIsr\fP after an initial \fIsr\fP is found will be highlighted until
@smallbook
@set EDITION 0.1
@set VERSION 1.3.10
-@set UPDATED 30 Mar 2006
+@set UPDATED 4 Apr 2006
@dircategory Editors
@direntry
@code{^([ \t]*[|>:@}#])+}
@end quotation
-if regular expression support is available, or ``> '' otherwise. Note
-that @code{\t} above stands for a literal Tab character.
+if extended regular expression support is available, or ``> ''
+otherwise. Note that @code{\t} above stands for a literal Tab
+character.
@item -R, --restricted
Restricted mode: Don't read or write to any file not specified on the
@section The Statusbar
The statusbar is located three lines from the bottom of the screen (or
-the bottom line in Expert Mode. @xref{Expert Mode}, for more info).
-
-The Statusbar shows important and informational messages. Any error
-messages that occur from using the editor will appear on the statusbar.
-Any questions that are asked of the user will be asked on the statusbar,
-and any user input (search strings, file names, etc) will be input on
-the statusbar.
+the bottom line in Expert Mode. @xref{Expert Mode}, for more info). It
+shows important and informational messages. Any error messages that
+occur from using the editor will appear on the statusbar. Any questions
+that are asked of the user will be asked on the statusbar, and any user
+input (search strings, file names, etc.) will be input on the statusbar.
@node Shortcut Lists, , The Statusbar, Editor Basics
@section Shortcut Lists
projects / nano.git / commitdiff