Linux Manual Pages development
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: [PATCH 06/10] suffixes.7: srcfix
Date: Sat, 31 Aug 2024 22:25:48 -0500	[thread overview]
Message-ID: <20240901032548.olkeoqjwpj76h42b@illithid> (raw)
In-Reply-To: <5bec58a0a261f834a2fc29d471b0b984822905b7.1725161054.git.g.branden.robinson@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1811 bytes --]

Prepare for `MR` macro migration.

Migrate man page cross references in table rows from using font
selection escape sequences to font alternation macros to set man page
cross references.

These are a handful of cases that made a sed(1)-scripted migration
ordering-dependent with its substitution ('s') commands.

Signed-off-by: "G. Branden Robinson" <g.branden.robinson@gmail.com>
---
 man/man7/suffixes.7 | 18 +++++++++++++++---
 1 file changed, 15 insertions(+), 3 deletions(-)

diff --git a/man/man7/suffixes.7 b/man/man7/suffixes.7
index 657f82cde..1341066bb 100644
--- a/man/man7/suffixes.7
+++ b/man/man7/suffixes.7
@@ -94,7 +94,11 @@ .SH DESCRIPTION
 \&.def	other definition files
 \&.desc	initial part of mail message unpacked with
 \&	\fBmunpack\fP(1)
-\&.diff	file differences (\fBdiff\fP(1) command output)
+\&.diff	T{
+file differences (\c
+.BR diff (1)
+command output)
+T}
 \&.dir	dbm data base directory file
 \&.doc	documentation file
 \&.dsc	Debian Source Control (source package)
@@ -109,7 +113,10 @@ .SH DESCRIPTION
 \&.f90	Fortran 90 source
 \&.fas	precompiled Common-Lisp
 \&.fi	Fortran include files
-\&.fig	FIG image file (used by \fBxfig\fP(1))
+\&.fig	T{
+FIG image file (used by
+.BR xfig (1))
+T}
 \&.fmt	TeX format file
 \&.gif	Compuserve Graphics Image File format
 \&.gmo	GNU format message catalog
@@ -250,7 +257,12 @@ .SH DESCRIPTION
 \&.xs	Perl xsub file produced by h2xs
 \&.xsl	XSL stylesheet
 \&.y	\fByacc\fP(1) or \fBbison\fP(1) (parser generator) files
-\&.z	File compressed using \fBpack\fP(1) (or an old \fBgzip\fP(1))
+\&.z	T{
+File compressed using
+.BR pack (1)
+(or an old
+.BR gzip (1))
+T}
 \&.zip	\fBzip\fP(1) archive
 \&.zoo	\fBzoo\fP(1) archive
 \&\[ti]	Emacs or \fBpatch\fP(1) backup file
-- 
2.30.2


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2024-09-01  3:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5bec58a0a261f834a2fc29d471b0b984822905b7.1725161054.git.g.branden.robinson@gmail.com>
2024-09-01  3:25 ` [PATCH 02/10] namespaces.7: srcfix G. Branden Robinson
2024-09-01  3:25 ` [PATCH 03/10] wctrans.3, wctype.3: srcfix G. Branden Robinson
2024-09-01  3:25 ` [PATCH 04/10] utmp.5: ffix G. Branden Robinson
2024-09-01  3:25 ` [PATCH 05/10] utmp.5: srcfix G. Branden Robinson
2024-09-01  3:25 ` G. Branden Robinson [this message]
2024-09-01  3:25 ` [PATCH 07/10] lirc.4: srcfix G. Branden Robinson
2024-09-01  3:26 ` [PATCH 08/10] console_codes.4, inode.7: srcfix G. Branden Robinson
2024-09-01  8:33   ` Alejandro Colomar
2024-09-01  3:26 ` [PATCH 09/10] man/: srcfix (1/2) G. Branden Robinson
2024-09-01  8:35   ` Alejandro Colomar
2024-09-01  3:26 ` [PATCH 10/10] man/: srcfix (2/2) G. Branden Robinson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240901032548.olkeoqjwpj76h42b@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox