nano

nano with my custom patches
git clone git://bsandro.tech/nano
Log | Files | Refs | README | LICENSE

commit 7681090c12d7553083e8aeff5bf74b7b28fa5692
parent 866490c41f5e123ce4d0239223203db1f44e0ecb
Author: Benno Schulenberg <bensberg@telfort.nl>
Date:   Thu, 16 Feb 2023 11:02:15 +0100

docs: clarify that a fileregex is matched against the absolute filename

Diffstat:
Mdoc/nano.texi | 7++++---
Mdoc/nanorc.5 | 7++++---
2 files changed, 8 insertions(+), 6 deletions(-)

diff --git a/doc/nano.texi b/doc/nano.texi @@ -1235,9 +1235,10 @@ will be added to this syntax, until a new @code{syntax} command is encountered. When @command{nano} is run, this syntax will be automatically -activated if the current filename matches the extended regular -expression @var{fileregex}. Or the syntax can be explicitly -activated by using the @option{-Y} or @option{--syntax} +activated (for the relevant buffer) if the absolute filename +matches the extended regular expression @var{fileregex}. +Or the syntax can be explicitly activated (for all buffers) +by using the @option{-Y} or @option{--syntax} command-line option followed by the @var{name}. The @code{default} syntax is special: it takes no @var{fileregex}, diff --git a/doc/nanorc.5 b/doc/nanorc.5 @@ -439,9 +439,10 @@ will be added to this syntax, until a new \fBsyntax\fR command is encountered. .sp When \fBnano\fR is run, this syntax will be automatically -activated if the current filename matches the extended regular -expression \fIfileregex\fR. Or the syntax can be explicitly -activated by using the \fB\-Y\fR or \fB\-\-syntax\fR +activated (for the relevant buffer) if the absolute filename +matches the extended regular expression \fIfileregex\fR. +Or the syntax can be explicitly activated (for all buffers) +by using the \fB\-Y\fR or \fB\-\-syntax\fR command-line option followed by the \fIname\fR. .sp The syntax \fBdefault\fP is special: it takes no \fIfileregex\fR,