From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 1/4] fts.3, div_t.3type: ffix
Date: Tue, 16 Jan 2024 16:21:58 +0100 [thread overview]
Message-ID: <ZaafFkmn2sJUmUZb@debian> (raw)
In-Reply-To: <20240116133940.jsgccc7ifzvlu2ol@illithid>
[-- Attachment #1: Type: text/plain, Size: 2284 bytes --]
Hi Branden,
On Tue, Jan 16, 2024 at 07:39:40AM -0600, G. Branden Robinson wrote:
> Break lines containing a parametric prefix to a man page name into two
> lines, using distinct font alternation macros and the `\c` escape
> sequence to "connect" the output. This prepares for adoption of the
> `MR` man(7) macro in groff 1.23.0.
>
> The style seen here assumes that the typeface used for man page names is
> bold, which is ahistorical and which the `MR` feature makes
> configurable. It might be better to recast this shorthand into English.
>
> Signed-off-by: "G. Branden Robinson" <g.branden.robinson@gmail.com>
I've applied patches 1, 2, and 4 from this set.
Have a lovely day,
Alex
> ---
> man3/fts.3 | 12 ++++++++----
> man3type/div_t.3type | 3 ++-
> 2 files changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/man3/fts.3 b/man3/fts.3
> index ae2fdfcbc..d2c520450 100644
> --- a/man3/fts.3
> +++ b/man3/fts.3
> @@ -187,7 +187,8 @@ .SH DESCRIPTION
> .TP
> .B FTS_NS
> A file for which no
> -.RB [ l ] stat (2)
> +.RB [ l ]\c
> +.BR stat (2)
> information was available.
> The contents of the
> .I fts_statp
> @@ -198,7 +199,8 @@ .SH DESCRIPTION
> .TP
> .B FTS_NSOK
> A file for which no
> -.RB [ l ] stat (2)
> +.RB [ l ]\c
> +.BR stat (2)
> information was requested.
> The contents of the
> .I fts_statp
> @@ -329,7 +331,8 @@ .SH DESCRIPTION
> .TP
> .I fts_statp
> A pointer to
> -.RB [ l ] stat (2)
> +.RB [ l ]\c
> +.BR stat (2)
> information for the file.
> .\" .El
> .P
> @@ -754,7 +757,8 @@ .SH ERRORS
> .BR opendir (3),
> .BR readdir (3),
> and
> -.RB [ l ] stat (2).
> +.RB [ l ]\c
> +.BR stat (2).
> .P
> In addition,
> .BR fts_children (),
> diff --git a/man3type/div_t.3type b/man3type/div_t.3type
> index 857dae17e..7abbb7616 100644
> --- a/man3type/div_t.3type
> +++ b/man3type/div_t.3type
> @@ -40,7 +40,8 @@ .SH SYNOPSIS
> .SH DESCRIPTION
> .RI [[ l ] l ] div_t
> is the type of the value returned by the
> -.RB [[ l ] l ] div (3)
> +.RB [[ l ] l ]\c
> +.BR div (3)
> function.
> .P
> .I imaxdiv_t
> --
> 2.30.2
>
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-01-16 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 13:39 [PATCH 1/4] fts.3, div_t.3type: ffix G. Branden Robinson
2024-01-16 15:21 ` Alejandro Colomar [this message]
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=ZaafFkmn2sJUmUZb@debian \
--to=alx@kernel.org \
--cc=g.branden.robinson@gmail.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).