- Moved nano.1 color and syntax sections to nanorc, pointed nano.1 to nanorc.5 for initialization file. Changed nanorc.5 variables to be italics to match nano.1. Added nanorc.5.html to CVS tree
git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@1461 35c25a1d-7b9e-4130-9fde-d3aeb78583b8master
parent
2e39c1c283
commit
4f989faa6e
|
@ -87,6 +87,10 @@ CVS code
|
||||||
bracketed to underlined to emphasize that they are not
|
bracketed to underlined to emphasize that they are not
|
||||||
optional.
|
optional.
|
||||||
- Add SEE ALSO section (Jordi).
|
- Add SEE ALSO section (Jordi).
|
||||||
|
- Moved nano.1 color and syntax sections to nanorc, pointed
|
||||||
|
nano.1 to nanorc.5 for initialization file. Changed
|
||||||
|
nanorc.5 variables to be italics to match nano.1. Added
|
||||||
|
nanorc.5.html to CVS tree.
|
||||||
- nanorc.5:
|
- nanorc.5:
|
||||||
- Add nanorc manpage, with descriptions of all available commands
|
- Add nanorc manpage, with descriptions of all available commands
|
||||||
(Jordi).
|
(Jordi).
|
||||||
|
|
|
@ -25,8 +25,8 @@ MAKEINFO = makeinfo --no-split
|
||||||
|
|
||||||
EXTRA_DIST = ABOUT-NLS AUTHORS BUGS COPYING ChangeLog INSTALL NEWS \
|
EXTRA_DIST = ABOUT-NLS AUTHORS BUGS COPYING ChangeLog INSTALL NEWS \
|
||||||
README THANKS TODO config.rpath install-sh missing \
|
README THANKS TODO config.rpath install-sh missing \
|
||||||
mkinstalldirs nano.1.html faq.html nanorc.sample nano.spec \
|
mkinstalldirs nano.1.html nanorc.5.html faq.html \
|
||||||
$(man_MANS)
|
nanorc.sample nano.spec $(man_MANS)
|
||||||
|
|
||||||
SUBDIRS = po m4
|
SUBDIRS = po m4
|
||||||
|
|
||||||
|
|
42
nano.1
42
nano.1
|
@ -144,45 +144,9 @@ Ignored, for compatibility with Pico.
|
||||||
|
|
||||||
.SH INITIALIZATION FILE
|
.SH INITIALIZATION FILE
|
||||||
\fBnano\fP will read initialization files in the following
|
\fBnano\fP will read initialization files in the following
|
||||||
order: $SYSCONFDIR/nanorc, then ~/.nanorc. Please see the example
|
order: $SYSCONFDIR/nanorc, then ~/.nanorc. Please see nanorc(5) and
|
||||||
file \fBnanorc.sample\fP which should be provided with \fBnano\fP.
|
the example file \fBnanorc.sample\fP which should be provided with
|
||||||
All lines beginning with a hash symbol (
|
\fBnano\fP.
|
||||||
#
|
|
||||||
) are considered comments
|
|
||||||
and will be ignored. The following commands are understood in the
|
|
||||||
initialization file:
|
|
||||||
.TP
|
|
||||||
.B [un]set \fIoption\fP [\fIvalue\fP]
|
|
||||||
Set (or unset) the flag \fIoption\fP. Any long option listed above can
|
|
||||||
be set or unset by removing the leading dashes (e.g. "set nowrap"). If
|
|
||||||
the option takes an argument it will be set to \fIvalue\fP.
|
|
||||||
.PP
|
|
||||||
\fBCOLOR SYNTAX HIGHLIGHTING\fP (if supported by your curses library)
|
|
||||||
.PP
|
|
||||||
.TP
|
|
||||||
.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 statements
|
|
||||||
will apply to \fIsyntax\fP until a new syntax is defined.
|
|
||||||
.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 optional background
|
|
||||||
color \fIbgcolor\fP. 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. If your
|
|
||||||
terminal supports transparency, not specifying a \fIbgcolor\fP tells
|
|
||||||
\fBnano\fP to attempt to use a transparent background.
|
|
||||||
.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 optional
|
|
||||||
background color \fIbgcolor\fP. 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 the first
|
|
||||||
instance of \fIer\fP.
|
|
||||||
\fI
|
|
||||||
|
|
||||||
.SH NOTES
|
.SH NOTES
|
||||||
\fBnano\fP will try to dump the buffer into an emergency file in some
|
\fBnano\fP will try to dump the buffer into an emergency file in some
|
||||||
|
|
81
nano.1.html
81
nano.1.html
|
@ -3,15 +3,17 @@ Content-type: text/html
|
||||||
<HTML><HEAD><TITLE>Manpage of NANO</TITLE>
|
<HTML><HEAD><TITLE>Manpage of NANO</TITLE>
|
||||||
</HEAD><BODY>
|
</HEAD><BODY>
|
||||||
<H1>NANO</H1>
|
<H1>NANO</H1>
|
||||||
Section: User Commands (1)<BR>Updated: November 1, 2002<BR><A HREF="#index">Index</A>
|
Section: User Commands (1)<BR>Updated: February 9, 2003<BR><A HREF="#index">Index</A>
|
||||||
<A HREF="http://localhost/cgi-bin/man/man2html">Return to Main Contents</A><HR>
|
<A HREF="http://localhost/cgi-bin/man/man2html">Return to Main Contents</A><HR>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
<P>
|
||||||
<A NAME="lbAB"> </A>
|
<A NAME="lbAB"> </A>
|
||||||
<H2>NAME</H2>
|
<H2>NAME</H2>
|
||||||
|
|
||||||
nano - Nano's ANOther editor, an enhanced free Pico clone
|
nano - Nano's ANOther editor, an enhanced free Pico clone
|
||||||
|
<P>
|
||||||
<A NAME="lbAC"> </A>
|
<A NAME="lbAC"> </A>
|
||||||
<H2>SYNOPSIS</H2>
|
<H2>SYNOPSIS</H2>
|
||||||
|
|
||||||
|
@ -21,6 +23,7 @@ nano - Nano's ANOther editor, an enhanced free Pico clone
|
||||||
|
|
||||||
<BR>
|
<BR>
|
||||||
|
|
||||||
|
<P>
|
||||||
<A NAME="lbAD"> </A>
|
<A NAME="lbAD"> </A>
|
||||||
<H2>DESCRIPTION</H2>
|
<H2>DESCRIPTION</H2>
|
||||||
|
|
||||||
|
@ -35,6 +38,7 @@ Pico, the default editor included in the non-free Pine package. Rather
|
||||||
than just copying Pico's look and feel, <B>nano</B> also implements some
|
than just copying Pico's look and feel, <B>nano</B> also implements some
|
||||||
missing (or disabled by default) features in Pico, such as "search and
|
missing (or disabled by default) features in Pico, such as "search and
|
||||||
replace" and "go to line number".
|
replace" and "go to line number".
|
||||||
|
<P>
|
||||||
<A NAME="lbAE"> </A>
|
<A NAME="lbAE"> </A>
|
||||||
<H2>OPTIONS</H2>
|
<H2>OPTIONS</H2>
|
||||||
|
|
||||||
|
@ -180,61 +184,17 @@ Enable suspend ability.
|
||||||
|
|
||||||
<DD>
|
<DD>
|
||||||
Ignored, for compatibility with Pico.
|
Ignored, for compatibility with Pico.
|
||||||
|
<P>
|
||||||
</DL>
|
</DL>
|
||||||
<A NAME="lbAF"> </A>
|
<A NAME="lbAF"> </A>
|
||||||
<H2>INITIALIZATION FILE</H2>
|
<H2>INITIALIZATION FILE</H2>
|
||||||
|
|
||||||
<B>nano</B> will read initialization files in the following
|
<B>nano</B> will read initialization files in the following
|
||||||
order: $SYSCONFDIR/nanorc, then ~/.nanorc. Please see the example
|
order: $SYSCONFDIR/nanorc, then ~/.nanorc. Please see <A HREF="http://localhost/cgi-bin/man/man2html?5+nanorc">nanorc</A>(5) and
|
||||||
file <B>nanorc.sample</B> which should be provided with <B>nano</B>.
|
the example file <B>nanorc.sample</B> which should be provided with
|
||||||
All lines beginning with a hash symbol (
|
<B>nano</B>.
|
||||||
#
|
|
||||||
) are considered comments
|
|
||||||
and will be ignored. The following commands are understood in the
|
|
||||||
initialization file:
|
|
||||||
<DL COMPACT>
|
|
||||||
<DT><B>[un]set </B><I>option</I> [<I>value</I>]
|
|
||||||
|
|
||||||
<DD>
|
|
||||||
Set (or unset) the flag <I>option</I>. Any long option listed above can
|
|
||||||
be set or unset by removing the leading dashes (e.g. "set nowrap"). If
|
|
||||||
the option takes an argument it will be set to <I>value</I>.
|
|
||||||
</DL>
|
|
||||||
<P>
|
<P>
|
||||||
|
<A NAME="lbAG"> </A>
|
||||||
<B>COLOR SYNTAX HIGHLIGHTING</B> (if supported by your curses library)
|
|
||||||
<P>
|
|
||||||
|
|
||||||
<DL COMPACT>
|
|
||||||
<DT><B>syntax </B><I>str</I> [<I>fileregex</I> ... ]
|
|
||||||
|
|
||||||
<DD>
|
|
||||||
Defines a syntax named <I>str</I> which can be activated via the
|
|
||||||
<B>-Y</B> flag, or will be automatically activated if the current
|
|
||||||
filename matches <I>fileregex</I>. All following <B>color</B> statements
|
|
||||||
will apply to <I>syntax</I> until a new syntax is defined.
|
|
||||||
<DT><B>color </B><I>fgcolor</I>[,<I>bgcolor</I>] <I>regex</I> ...
|
|
||||||
|
|
||||||
<DD>
|
|
||||||
For the currently defined syntax, display all expressions matching
|
|
||||||
<I>regex</I> with foreground color <I>fgcolor</I> and optional background
|
|
||||||
color <I>bgcolor</I>. 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. If your
|
|
||||||
terminal supports transparency, not specifying a <I>bgcolor</I> tells
|
|
||||||
<B>nano</B> to attempt to use a transparent background.
|
|
||||||
<DT><B>color </B><I>fgcolor</I>[,<I>bgcolor</I>] start=<I>sr</I> end=<I>er</I>
|
|
||||||
|
|
||||||
<DD>
|
|
||||||
Display expressions which start with <I>sr</I> and end with <I>er</I>
|
|
||||||
with foreground color <I>fgcolor</I> and optional
|
|
||||||
background color <I>bgcolor</I>. This allows syntax highlighting to span
|
|
||||||
multiple lines. Note that all subsequent instances of <I>sr</I> after
|
|
||||||
an initial <I>sr</I> is found will be highlighted until the first
|
|
||||||
instance of <I>er</I>.
|
|
||||||
<I>
|
|
||||||
</DL>
|
|
||||||
</I><A NAME="lbAG"> </A>
|
|
||||||
<H2>NOTES</H2>
|
<H2>NOTES</H2>
|
||||||
|
|
||||||
<B>nano</B> will try to dump the buffer into an emergency file in some
|
<B>nano</B> will try to dump the buffer into an emergency file in some
|
||||||
|
@ -246,6 +206,7 @@ name already exists in the current directory, ".save" and a number (e.
|
||||||
".save.1") will be suffixed to the current filename in order to make it
|
".save.1") will be suffixed to the current filename in order to make it
|
||||||
unique. In multibuffer mode, <B>nano</B> will write all the open buffers
|
unique. In multibuffer mode, <B>nano</B> will write all the open buffers
|
||||||
to the respective emergency files.
|
to the respective emergency files.
|
||||||
|
<P>
|
||||||
<A NAME="lbAH"> </A>
|
<A NAME="lbAH"> </A>
|
||||||
<H2>BUGS</H2>
|
<H2>BUGS</H2>
|
||||||
|
|
||||||
|
@ -263,11 +224,24 @@ The <B>nano</B> mailing list is available from
|
||||||
|
|
||||||
To subscribe, email to <A HREF="mailto:nano-devel-request@gnu.org">nano-devel-request@gnu.org</A> with a
|
To subscribe, email to <A HREF="mailto:nano-devel-request@gnu.org">nano-devel-request@gnu.org</A> with a
|
||||||
subject of "subscribe".
|
subject of "subscribe".
|
||||||
|
<P>
|
||||||
<A NAME="lbAI"> </A>
|
<A NAME="lbAI"> </A>
|
||||||
<H2>HOMEPAGE</H2>
|
<H2>HOMEPAGE</H2>
|
||||||
|
|
||||||
<A HREF="http://www.nano-editor.org">http://www.nano-editor.org</A>
|
<A HREF="http://www.nano-editor.org/">http://www.nano-editor.org/</A>
|
||||||
|
<P>
|
||||||
<A NAME="lbAJ"> </A>
|
<A NAME="lbAJ"> </A>
|
||||||
|
<H2>SEE ALSO</H2>
|
||||||
|
|
||||||
|
|
||||||
|
<DL COMPACT>
|
||||||
|
<DT><B><A HREF="http://localhost/cgi-bin/man/man2html?5+nanorc">nanorc</A></B>(5)<DD>
|
||||||
|
</DL>
|
||||||
|
<P>
|
||||||
|
|
||||||
|
<I>/usr/share/doc/nano/</I> (or equivalent on your system)
|
||||||
|
<P>
|
||||||
|
<A NAME="lbAK"> </A>
|
||||||
<H2>AUTHOR</H2>
|
<H2>AUTHOR</H2>
|
||||||
|
|
||||||
Chris Allegretta <<A HREF="mailto:chrisa@asty.org">chrisa@asty.org</A>>, et al (see AUTHORS and THANKS for
|
Chris Allegretta <<A HREF="mailto:chrisa@asty.org">chrisa@asty.org</A>>, et al (see AUTHORS and THANKS for
|
||||||
|
@ -288,12 +262,13 @@ used by others).
|
||||||
<DT><A HREF="#lbAG">NOTES</A><DD>
|
<DT><A HREF="#lbAG">NOTES</A><DD>
|
||||||
<DT><A HREF="#lbAH">BUGS</A><DD>
|
<DT><A HREF="#lbAH">BUGS</A><DD>
|
||||||
<DT><A HREF="#lbAI">HOMEPAGE</A><DD>
|
<DT><A HREF="#lbAI">HOMEPAGE</A><DD>
|
||||||
<DT><A HREF="#lbAJ">AUTHOR</A><DD>
|
<DT><A HREF="#lbAJ">SEE ALSO</A><DD>
|
||||||
|
<DT><A HREF="#lbAK">AUTHOR</A><DD>
|
||||||
</DL>
|
</DL>
|
||||||
<HR>
|
<HR>
|
||||||
This document was created by
|
This document was created by
|
||||||
<A HREF="http://localhost/cgi-bin/man/man2html">man2html</A>,
|
<A HREF="http://localhost/cgi-bin/man/man2html">man2html</A>,
|
||||||
using the manual pages.<BR>
|
using the manual pages.<BR>
|
||||||
Time: 14:15:34 GMT, February 04, 2003
|
Time: 04:08:28 GMT, February 13, 2003
|
||||||
</BODY>
|
</BODY>
|
||||||
</HTML>
|
</HTML>
|
||||||
|
|
48
nanorc.5
48
nanorc.5
|
@ -49,14 +49,14 @@ Constantly update the cursor position.
|
||||||
\fBset/unset cut\fP
|
\fBset/unset cut\fP
|
||||||
Use cut to end of line with ^K by default.
|
Use cut to end of line with ^K by default.
|
||||||
.TP
|
.TP
|
||||||
\fBset fill n\fP
|
\fBset fill \fIn\fP\fP
|
||||||
Set fill cols to n.
|
Set the column where lines will be wrapped at to \fIn\fP.
|
||||||
.TP
|
.TP
|
||||||
\fBset/unset keypad\fP
|
\fBset/unset keypad\fP
|
||||||
Use alternate keypad routines.
|
Use alternate keypad routines.
|
||||||
.TP
|
.TP
|
||||||
\fBset/unset multibuffer\fP
|
\fBset/unset multibuffer\fP
|
||||||
Allow multiple file buffers.
|
Allow inserting files into their own buffers.
|
||||||
.TP
|
.TP
|
||||||
\fBset/unset noconvert\fP
|
\fBset/unset noconvert\fP
|
||||||
Don't convert files from DOS/Mac format.
|
Don't convert files from DOS/Mac format.
|
||||||
|
@ -70,13 +70,13 @@ Don't display the help lists at the bottom of the screen.
|
||||||
\fBset/unset nowrap\fP
|
\fBset/unset nowrap\fP
|
||||||
Don't wrap text at all.
|
Don't wrap text at all.
|
||||||
.TP
|
.TP
|
||||||
\fBset operatingdir "directory"\fP
|
\fBset operatingdir "\fIdirectory\fP"\fP
|
||||||
Set operating directory (chroots the user to "directory" and below).
|
Set operating directory (chroots the user to \fIdirectory\fP and below).
|
||||||
.TP
|
.TP
|
||||||
\fBset/unset preserve\fP
|
\fBset/unset preserve\fP
|
||||||
Preserve the XON and XOFF keys (^Q and ^S).
|
Preserve the XON and XOFF keys (^Q and ^S).
|
||||||
.TP
|
.TP
|
||||||
\fBset quotestr "string"\fP
|
\fBset quotestr "\fIstring\fP"\fP
|
||||||
The email-quote string. This is a "regular expression" if your
|
The email-quote string. This is a "regular expression" if your
|
||||||
system supports them, otherwise a literal string.
|
system supports them, otherwise a literal string.
|
||||||
Default value is set quotestr "^([ \t]*[|>:}#])+" if you have regexps,
|
Default value is set quotestr "^([ \t]*[|>:}#])+" if you have regexps,
|
||||||
|
@ -88,14 +88,15 @@ Do regular expression searches by default.
|
||||||
\fBset/unset smooth\fP
|
\fBset/unset smooth\fP
|
||||||
Use smooth scrolling by default.
|
Use smooth scrolling by default.
|
||||||
.TP
|
.TP
|
||||||
\fBset speller aspell\fP
|
\fBset speller \fIspellprog\fP\fP
|
||||||
Use this spelling checker instead of the default (spell).
|
Use spelling checker \fIspellprog\fP instead of the default (spell).
|
||||||
.TP
|
.TP
|
||||||
\fBset/unset suspend\fP
|
\fBset/unset suspend\fP
|
||||||
Allow nano to be suspended with ^Z.
|
Allow nano to be suspended with ^Z.
|
||||||
.TP
|
.TP
|
||||||
\fBset tabsize n\fP
|
\fBset tabsize \fIn\fP\fP
|
||||||
Use a tab size of n instead of the default (8); must be greater than 0.
|
Use a tab size of \fIn\fP instead of the default (8); must be greater
|
||||||
|
than 0.
|
||||||
.TP
|
.TP
|
||||||
\fBset/unset tempfile\fP
|
\fBset/unset tempfile\fP
|
||||||
Save automatically on exit, don't prompt.
|
Save automatically on exit, don't prompt.
|
||||||
|
@ -106,14 +107,29 @@ Enable ~/.nano_history for saving and reading search/replace strings.
|
||||||
\fBset/unset view\fP
|
\fBset/unset view\fP
|
||||||
Disallow file modification.
|
Disallow file modification.
|
||||||
.TP
|
.TP
|
||||||
\fBsyntax "short description" "regexp"\fP
|
.B syntax "\fIstr\fP" ["\fIfileregex\fP" ... ]
|
||||||
Define a color syntax name and a regexp to associate files to it.
|
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 statements
|
||||||
|
will apply to \fIsyntax\fP until a new syntax is defined.
|
||||||
.TP
|
.TP
|
||||||
\fBcolor "foreground" "[background]" "regexp" ["regexp"...]\fP
|
.B color \fIfgcolor\fP[,\fIbgcolor\fP] "\fIregex\fP" ...
|
||||||
Define color rules for different strings. Specifying background is optional,
|
For the currently defined syntax, display all expressions matching
|
||||||
and you can define multiple regexps to a color rule.
|
\fIregex\fP with foreground color \fIfgcolor\fP and optional background
|
||||||
|
color \fIbgcolor\fP. 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. If your
|
||||||
|
terminal supports transparency, not specifying a \fIbgcolor\fP tells
|
||||||
|
\fBnano\fP to attempt to use a transparent background.
|
||||||
.TP
|
.TP
|
||||||
Every "syntax" command must be followed by one or more "color" rules.
|
.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 optional
|
||||||
|
background color \fIbgcolor\fP. 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 the first
|
||||||
|
instance of \fIer\fP.
|
||||||
|
\fI
|
||||||
|
|
||||||
.SH SEE ALSO
|
.SH SEE ALSO
|
||||||
.PD 0
|
.PD 0
|
||||||
|
|
|
@ -0,0 +1,162 @@
|
||||||
|
Content-type: text/html
|
||||||
|
|
||||||
|
<HTML><HEAD><TITLE>Manpage of NANORC</TITLE>
|
||||||
|
</HEAD><BODY>
|
||||||
|
<H1>NANORC</H1>
|
||||||
|
Section: File Formats (5)<BR>Updated: February 9, 2003<BR><A HREF="#index">Index</A>
|
||||||
|
<A HREF="http://localhost/cgi-bin/man/man2html">Return to Main Contents</A><HR>
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
<A NAME="lbAB"> </A>
|
||||||
|
<H2>NAME</H2>
|
||||||
|
|
||||||
|
nanorc - GNU nano's rcfile
|
||||||
|
<A NAME="lbAC"> </A>
|
||||||
|
<H2>SYNOPSIS</H2>
|
||||||
|
|
||||||
|
<B>/etc/nanorc</B>
|
||||||
|
|
||||||
|
<B>$HOME/.nanorc</B>
|
||||||
|
|
||||||
|
<BR>
|
||||||
|
|
||||||
|
<A NAME="lbAD"> </A>
|
||||||
|
<H2>DESCRIPTION</H2>
|
||||||
|
|
||||||
|
This manual page documents GNU <B>nano</B>'s rcfile.
|
||||||
|
<P>
|
||||||
|
|
||||||
|
<B>nano</B> is a small, free and friendly editor which aims to replace
|
||||||
|
Pico, the default editor included in the non-free Pine package. Rather
|
||||||
|
than just copying Pico's look and feel, <B>nano</B> also implements some
|
||||||
|
missing (or disabled by default) features in Pico, such as "search and
|
||||||
|
replace" and "go to line number".
|
||||||
|
<P>
|
||||||
|
<A NAME="lbAE"> </A>
|
||||||
|
<H2>OPTIONS</H2>
|
||||||
|
|
||||||
|
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" and "color" keywords
|
||||||
|
are used to define syntax highlighting rules for different text patterns.
|
||||||
|
GNU nano will read one command per line.
|
||||||
|
<P>
|
||||||
|
Options in rcfiles take precedence over nano's defaults, and command line
|
||||||
|
options override rcfile settings.
|
||||||
|
<P>
|
||||||
|
The supported commands and arguments are:
|
||||||
|
<P>
|
||||||
|
<DL COMPACT>
|
||||||
|
<DT><B>set/unset autoindent</B><DD>
|
||||||
|
Use auto-indentation.
|
||||||
|
<DT><B>set/unset backup</B><DD>
|
||||||
|
Create backup files in filename~.
|
||||||
|
<DT><B>set/unset const</B><DD>
|
||||||
|
Constantly update the cursor position.
|
||||||
|
<DT><B>set/unset cut</B><DD>
|
||||||
|
Use cut to end of line with ^K by default.
|
||||||
|
<DT><B>set fill </B><I>n</I><DD>
|
||||||
|
Set the column where lines will be wrapped at to <I>n</I>.
|
||||||
|
<DT><B>set/unset keypad</B><DD>
|
||||||
|
Use alternate keypad routines.
|
||||||
|
<DT><B>set/unset multibuffer</B><DD>
|
||||||
|
Allow inserting files into their own buffers.
|
||||||
|
<DT><B>set/unset noconvert</B><DD>
|
||||||
|
Don't convert files from DOS/Mac format.
|
||||||
|
<DT><B>set/unset nofollow</B><DD>
|
||||||
|
Don't follow symlinks when writing files.
|
||||||
|
<DT><B>set/unset nohelp</B><DD>
|
||||||
|
Don't display the help lists at the bottom of the screen.
|
||||||
|
<DT><B>set/unset nowrap</B><DD>
|
||||||
|
Don't wrap text at all.
|
||||||
|
<DT><B>set operatingdir "</B><I>directory</I>"<DD>
|
||||||
|
Set operating directory (chroots the user to <I>directory</I> and below).
|
||||||
|
<DT><B>set/unset preserve</B><DD>
|
||||||
|
Preserve the XON and XOFF keys (^Q and ^S).
|
||||||
|
<DT><B>set quotestr "</B><I>string</I>"<DD>
|
||||||
|
The email-quote string. This is a "regular expression" if your
|
||||||
|
system supports them, otherwise a literal string.
|
||||||
|
Default value is set quotestr "^([ ]*[|>:}#])+" if you have regexps,
|
||||||
|
otherwise set quotestr "> ".
|
||||||
|
<DT><B>set/unset regexp</B><DD>
|
||||||
|
Do regular expression searches by default.
|
||||||
|
<DT><B>set/unset smooth</B><DD>
|
||||||
|
Use smooth scrolling by default.
|
||||||
|
<DT><B>set speller </B><I>spellprog</I><DD>
|
||||||
|
Use spelling checker <I>spellprog</I> instead of the default (spell).
|
||||||
|
<DT><B>set/unset suspend</B><DD>
|
||||||
|
Allow nano to be suspended with ^Z.
|
||||||
|
<DT><B>set tabsize </B><I>n</I><DD>
|
||||||
|
Use a tab size of <I>n</I> instead of the default (8); must be greater
|
||||||
|
than 0.
|
||||||
|
<DT><B>set/unset tempfile</B><DD>
|
||||||
|
Save automatically on exit, don't prompt.
|
||||||
|
<DT><B>set/unset historylog</B><DD>
|
||||||
|
Enable ~/.nano_history for saving and reading search/replace strings.
|
||||||
|
<DT><B>set/unset view</B><DD>
|
||||||
|
Disallow file modification.
|
||||||
|
<DT><B>syntax </B><I>str</I> [<I>fileregex</I> ... ]
|
||||||
|
|
||||||
|
<DD>
|
||||||
|
Defines a syntax named <I>str</I> which can be activated via the
|
||||||
|
<B>-Y</B> flag, or will be automatically activated if the current
|
||||||
|
filename matches <I>fileregex</I>. All following <B>color</B> statements
|
||||||
|
will apply to <I>syntax</I> until a new syntax is defined.
|
||||||
|
<DT><B>color </B><I>fgcolor</I>[,<I>bgcolor</I>] <I>regex</I> ...
|
||||||
|
|
||||||
|
<DD>
|
||||||
|
For the currently defined syntax, display all expressions matching
|
||||||
|
<I>regex</I> with foreground color <I>fgcolor</I> and optional background
|
||||||
|
color <I>bgcolor</I>. 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. If your
|
||||||
|
terminal supports transparency, not specifying a <I>bgcolor</I> tells
|
||||||
|
<B>nano</B> to attempt to use a transparent background.
|
||||||
|
<DT><B>color </B><I>fgcolor</I>[,<I>bgcolor</I>] start=<I>sr</I> end=<I>er</I>
|
||||||
|
|
||||||
|
<DD>
|
||||||
|
Display expressions which start with <I>sr</I> and end with <I>er</I>
|
||||||
|
with foreground color <I>fgcolor</I> and optional
|
||||||
|
background color <I>bgcolor</I>. This allows syntax highlighting to span
|
||||||
|
multiple lines. Note that all subsequent instances of <I>sr</I> after
|
||||||
|
an initial <I>sr</I> is found will be highlighted until the first
|
||||||
|
instance of <I>er</I>.
|
||||||
|
<I>
|
||||||
|
<P>
|
||||||
|
</DL>
|
||||||
|
</I><A NAME="lbAF"> </A>
|
||||||
|
<H2>SEE ALSO</H2>
|
||||||
|
|
||||||
|
|
||||||
|
<DL COMPACT>
|
||||||
|
<DT><B><A HREF="http://localhost/cgi-bin/man/man2html?1+nano">nano</A></B>(1)<DD>
|
||||||
|
</DL>
|
||||||
|
<P>
|
||||||
|
|
||||||
|
<I>/usr/share/doc/nano/examples/nanorc.sample</I> (or equivalent on your system)
|
||||||
|
<A NAME="lbAG"> </A>
|
||||||
|
<H2>AUTHOR</H2>
|
||||||
|
|
||||||
|
Chris Allegretta <<A HREF="mailto:chrisa@asty.org">chrisa@asty.org</A>>, et al (see AUTHORS and THANKS for
|
||||||
|
details).
|
||||||
|
This manual page was written by Jordi Mallach <<A HREF="mailto:jordi@gnu.org">jordi@gnu.org</A>>.
|
||||||
|
<P>
|
||||||
|
|
||||||
|
<HR>
|
||||||
|
<A NAME="index"> </A><H2>Index</H2>
|
||||||
|
<DL>
|
||||||
|
<DT><A HREF="#lbAB">NAME</A><DD>
|
||||||
|
<DT><A HREF="#lbAC">SYNOPSIS</A><DD>
|
||||||
|
<DT><A HREF="#lbAD">DESCRIPTION</A><DD>
|
||||||
|
<DT><A HREF="#lbAE">OPTIONS</A><DD>
|
||||||
|
<DT><A HREF="#lbAF">SEE ALSO</A><DD>
|
||||||
|
<DT><A HREF="#lbAG">AUTHOR</A><DD>
|
||||||
|
</DL>
|
||||||
|
<HR>
|
||||||
|
This document was created by
|
||||||
|
<A HREF="http://localhost/cgi-bin/man/man2html">man2html</A>,
|
||||||
|
using the manual pages.<BR>
|
||||||
|
Time: 04:08:33 GMT, February 13, 2003
|
||||||
|
</BODY>
|
||||||
|
</HTML>
|
Loading…
Reference in New Issue