[PATCH 15/31] docs: consistently set file names in italics
"G. Branden Robinson" <[email protected]> Thu, 23 Apr 2026 17:59:20 -0500
| Newsgroups | gmane.editors.nano.devel |
|---|---|
| Message-ID | <20260423225920.dnt4pumffql5s7av@illithid> |
Also protect them from hyphenation and mark lengthy file names with
hyphenless break points.
groff_man_style(7):
Fundamental concepts
...
... Breaks can occur at explicit hyphens, at \% or \: escape
sequences (see subsection “Portability” below), or at predetermined
locations in a word if automatic hyphenation is enabled (see the -rHY
option in section “Options” below).
...
Portability
...
\: Insert a non‐printing break point. A word can break
where \: appears, but a hyphen glyph is not written to
the output if it does. The remainder of the word is
subject to hyphenation as normal. You can use \: and \%
in combination to control breaking of a file name or URI
or to permit hyphenation only after certain explicit
hyphens within a word. See subsection “Hyperlink macros”
above for an example.
\: is a GNU extension also supported by Heirloom Doctools
troff 050915 (September 2005), mandoc 1.13.1
(2014‐08‐10), and neatroff (commit 399a4936, 2014‐02‐17),
but not by DWB, Plan 9, or Solaris troffs.
---
doc/nano.1 | 14 +++++++-------
doc/nanorc.5 | 6 +++---
2 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/doc/nano.1 b/doc/nano.1
index 38c7c285..2141e155 100644
--- a/doc/nano.1
+++ b/doc/nano.1
@@ -148,7 +148,7 @@ .SH OPTIONS
This can be overridden for specific elements by setting the options
\fB\%titlecolor\fR, \fB\%statuscolor\fR, \fB\%promptcolor\fR,
\fB\%minicolor\fR, \fB\%keycolor\fR, \fB\%numbercolor\fR, and/or
-\fB\%selectedcolor\fR in your nanorc file. See \fBnanorc\fR(5).
+\fB\%selectedcolor\fR in your \fInanorc\fR file. See \fBnanorc\fR(5).
.TP
.BR \-E ", " \-\-tabstospaces
Convert each typed tab to spaces \[em] to the number of spaces
@@ -280,7 +280,7 @@ .SH OPTIONS
.TP
.BI \-f " file\fR, " \-\-rcfile= file
Read only this \fIfile\fR for setting nano's options, instead of reading
-both the system-wide and the user's nanorc files.
+both the system-wide and the user's \fInanorc\fR files.
.TP
.BR \-g ", " \-\-showcursor
Make the cursor visible in the file browser (putting it on the
@@ -458,12 +458,12 @@ .SH FILES
for setting its options and syntaxes and key bindings. Without that
option, \fBnano\fR reads two configuration files: first the system's
\fInanorc\fR (if it exists), and then the user's \fInanorc\fR (if it
-exists), either \fI\[ti]/.nanorc\fR or \fI$XDG_CONFIG_HOME/nano/nanorc\fR
-or \fI\[ti]/.config/nano/nanorc\fR, whichever is encountered first. See
+exists), either \fI\[ti]/.nanorc\fR or \%\fI$XDG_CONFIG_HOME/\:nano/\:nanorc\fR
+or \%\fI\[ti]/.config/\:nano/\:nanorc\fR, whichever is encountered first. See
.BR nanorc (5)
for more information on the possible contents of those files.
.P
-See \fI/usr/share/nano/\fR and \fI/usr/share/nano/extra/\fR
+See \fI/usr/\:share/\:nano/\fR and \fI/\:usr/\:share/\:nano/\:extra/\fR
for available syntax-coloring definitions.
.
.SH EXIT STATUS
@@ -480,7 +480,7 @@ .SH EXIT STATUS
.SH NOTES
Suspension is enabled by default, reachable via \fB\[ha]T\[ha]Z\fR.
(If you want a plain \fB\[ha]Z\fR to suspend nano, add
-\fBbind \[ha]Z suspend main\fR to your nanorc.)
+\fBbind \[ha]Z suspend main\fR to your \fInanorc\fR.)
.P
At a Yes-No prompt, \fB\[ha]Y\fR can be used for "Yes", \fB\[ha]N\fR for "No",
and \fB\[ha]A\fR for "All".
@@ -522,7 +522,7 @@ .SH BUGS
Savannah bug tracker
.UE .
.P
-When nano crashes, it saves any modified buffers to emergency .save files.
+When nano crashes, it saves any modified buffers to emergency \fI.save\fR files.
If you are able to reproduce the crash and you want to get a backtrace, define
the environment variable \fBNANO_NOCATCH\fR.
.
diff --git a/doc/nanorc.5 b/doc/nanorc.5
index d7422a0e..fd470e91 100644
--- a/doc/nanorc.5
+++ b/doc/nanorc.5
@@ -27,9 +27,9 @@ .SH DESCRIPTION
The \fInanorc\fR files contain the default settings for \fBnano\fR,
a small and friendly text editor. During startup, if \fB\-\-rcfile\fR
is not given, \fBnano\fR reads two files: first the system-wide settings,
-from \fI/etc/nanorc\fR (the exact path might be different on your system),
+from \fI/etc/\:nanorc\fR (the exact path might be different on your system),
and then the user-specific settings, either from \fI\[ti]/.nanorc\fR or from
-\fI$XDG_CONFIG_HOME/nano/nanorc\fR or from \fI\[ti]/.config/nano/nanorc\fR,
+\%\fI$XDG_CONFIG_HOME/\:nano/\:nanorc\fR or from \fI\[ti]/.config/\:nano/\:nanorc\fR,
whichever is encountered first. If \fB\-\-rcfile\fR is given,
\fBnano\fR reads just the specified settings file.
.
@@ -475,7 +475,7 @@ .SH SYNTAX HIGHLIGHTING
A complete explanation can be found in the manual page of GNU grep:
\fBman grep\fR.
.P
-Each regular expression in a \fBnanorc\fR file should be wrapped in
+Each regular expression in a \fInanorc\fR file should be wrapped in
double quotes (\fB""\fR). Multiple regular expressions can follow
each other on a line by separating them with blanks. This means that
a regular expression cannot contain a double quote followed by a blank.
--
2.30.2
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAmnqpEgACgkQ0Z6cfXEm bc7bdRAApUyuP94r2nmINBTXm6kMGG190P0QSgz5WCIQeDHaZK0OLTszlTLVm8m5 rYxXR1HoC6Gaw475BbPe5XArk1jPhlJ7pW2dsOCZDE2rLn3GnEZwG7eOW5gDGjes nfhoA3NzVKtFKUqeppcxajdKNspSC7MEUgxmMANpB3dnbu4h4LHok5w+ivDM0MTN 5a8BOpeFywMVwoqP1NsseumTnWceDwHtHx0k5HqCTLN7tkggMAw4anPG6vYHUZNV tG9MSulFYnPP6VxZ7QXsDbDlHfapjcuulM/UrXQCM517Zn1CmFqKEWnwx3BEOjdt lk8ufZVZa6PtwQ9FW8fc4QZn8XazGCDqZNpEjcsBOPuuxsvGYGkW6joqcOyXOQH3 Wbn63yPpfhN5ZqOUw5LUGsMuuMPKkiLIyf/43yRBsd5glNFi1IwfnA+YrculP6z+ 0MifcCN1tGihkNFQ3nL/WIE0Wf+P5IK8vHadqjF5Xnq/sWzJ7hbiCKrVUSOLDoxv LKi5cEPafWI5PZwxnsN8xHL2KJisPvjY+BaynMzo0LmJx5Z7kAquuMKNpJEdTU9G o7LhV6wKxR9Uq/tknR3kvCNFpUlizkEn/AEZZ4g1b6wgLVwq9A11OqZZQ2yDpB8v hZHhjL9RV4hEhy+3RJWZzxv/kGQ9EO6ILFJg9k08KWzC7EyKZzQ= =hGQV -----END PGP SIGNATURE-----