This parameter is determined by the "configure" script. It refers to a file name, so set it in italics, not bold or roman. It can be lengthy, so protect it from automatic hyphenation when it might appear non-initially on an output line. (Contrast with paragraph tags supplied to the `TP` macro, which always start an output line.)
While we're at it, revise markup.
* Favor man(7) font style macros over *roff font selection escape
sequences, except for man page cross references (because
man/make_sed.sh recognizes only certain patterns when rewriting such
cross references) and terms in the "NAME" section (because the
generated edit_man.sh script expects font selection escape sequences
when scraping terms thence to gather names for man page aliases).
* Quote (single-character) trailing punctuation arguments to man(7) font
alternation macros. The package does not require this; it avoids
false positives reported by one of Thomas Dickey's style-checking
scripts, per his communication.
---
man/term.7 | 7 ++++---
man/tic.1m | 13 +++++++++----
2 files changed, 13 insertions(+), 7 deletions(-)
diff --git a/man/term.7 b/man/term.7
index ac4ab6cfb..59e93e817 100644
--- a/man/term.7
+++ b/man/term.7
@@ -82,7 +82,7 @@ .SH DESCRIPTION
which you wish to override the system default type for your line.
.PP
Terminal type descriptions are stored as files of capability data underneath
-@TERMINFO@.
+.IR \%@TERMINFO@ "."
To browse a list of all terminal names recognized by the system, do
.sp
@TOE@ | more
@@ -96,8 +96,9 @@ .SH DESCRIPTION
@INFOCMP@ \fIentry_name\fP
.sp
where \fIentry_name\fP is the name of the type you wish to examine (and the
-name of its capability file the subdirectory of @TERMINFO@ named for its first
-letter).
+name of its capability file the subdirectory of
+.I \%@TERMINFO@
+named for its first letter).
This command dumps a capability file in the text format described by
\fBterminfo\fP(5).
.PP
diff --git a/man/tic.1m b/man/tic.1m
index 188b2c924..5e6585c9f 100644
--- a/man/tic.1m
+++ b/man/tic.1m
@@ -109,7 +109,8 @@ .SH DESCRIPTION
versus a "terminfo.db" file.
.PP
The results are normally placed
-in the system terminfo database \fB@TERMINFO@\fP.
+in the system terminfo database
+.IR \%@TERMINFO@ "."
The compiled terminal description can be placed
in a different terminfo database.
There are two ways to achieve this:
@@ -119,7 +120,8 @@ .SH DESCRIPTION
or by setting the variable \fI\%TERMINFO\fP
in your shell environment to a valid database location.
.bP
-Secondly, if \fB@TIC@\fP cannot write in \fI@TERMINFO@\fP
+Secondly, if \fB@TIC@\fP cannot write in
+.I \%@TERMINFO@
or the location specified using your \fI\%TERMINFO\fP variable,
it looks for the directory \fI$HOME/.terminfo\fP
(or hashed database \fI$HOME/.terminfo.db)\fP;
@@ -135,7 +137,8 @@ .SH DESCRIPTION
.bP
a compiled-in list of directories (@TERMINFO_DIRS@), and
.bP
-the system terminfo database (\fI@TERMINFO@\fP).
+the system terminfo database
+.RI \%( @TERMINFO@ ).
.PP
The \fIFetching Compiled Descriptions\fP section in the \fBterminfo\fR(5)
manual goes into further detail.
@@ -421,7 +424,9 @@ .SS Processing
.PP
When a \fBuse\fP=\fIentry\fP\-\fIname\fP field is discovered in a
terminal entry currently being compiled, \fB@TIC@\fP reads in the binary
-from \fB@TERMINFO@\fP to complete the entry.
+from
+.I \%@TERMINFO@
+to complete the entry.
(Entries created from
\fIfile\fP will be used first.
\fB@TIC@\fP duplicates the capabilities in
--
2.30.2
signature.asc
Description: PGP signature
