From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: linux-man@vger.kernel.org
Cc: "Alejandro Colomar" <alx@kernel.org>,
"Mark Wielaard" <mark@klomp.org>,
"Alexandra Hájková" <ahajkova@redhat.com>
Subject: man page base paragraph inset/indentation (was: [PATCH v3] close_range.2: Add _GNU_SOURCE and unistd.h to SYNOPSIS)
Date: Sun, 18 Feb 2024 08:14:47 -0600 [thread overview]
Message-ID: <20240218141447.q34tghthp7d4llpg@illithid> (raw)
In-Reply-To: <ZdIBa2VRKK_06f9X@debian>
[-- Attachment #1: Type: text/plain, Size: 2051 bytes --]
Hi folks,
At 2024-02-18T14:08:59+0100, Alejandro Colomar wrote:
> On Sun, Feb 18, 2024 at 01:00:35PM +0100, Mark Wielaard wrote:
> > Note that there is now one line which is > 80 chars.
> > You can fix that using this from the original fix,
> > that splits and indents the comment on two lines:
> >
> > > > +.BR "#include <linux/close_range.h>" " /* Definition of " CLOSE_RANGE_* "
> > > > +.BR "" " constants */"
>
> Ahhh, I see. I'm using groff from git (what will be groff-1.24.0 some
> day), which changes the default indentation from 7 to 5, which is why
> it fits in the line for me. Thanks for reporting that! I'll fix it
> in a moment.
This rendering parameter is now configurable, of course, to accommodate
people who prefer the "old" one. So when generating cat pages, doing
diffs, or similar, you can pass the following option to GNU troff(1):
-rBP=7n
This can be done for any version of GNU troff; versions of the GNU
man(7) macro package that are too told will simply (and silently) ignore
it, and use a base paragraph inset of 7n regardless.
Here's the NEWS item from the forthcoming groff 1.24.0.
o The an (man) and doc (mdoc) macro packages now support a `BP` register
to configure the ("base") paragraph inset amount; that is the amount
used by man(7) for paragraphs not within an `RS`/`RE` relative inset,
and in mdoc(7) for all paragraphs. Formerly, the `IN` register
configured this amount with other indentation and inset amount
parameters used by man(7). (In mdoc(7), it had no other purpose.)
The base paragraph indentation default is now 5n, corresponding to
that used by historical man(7) and mdoc(7) implementations going back
to Unix Version 7 (1979) and 4.3BSD-Reno (1990), respectively.
Ingo Schwarze has made a parallel change to mandoc(1), and I expect it
to show up in the next release thereof.
https://cvsweb.bsd.lv/mandoc/man_term.c?rev=1.244&content-type=text/x-cvsweb-markup&sortby=date
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-18 14:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 12:07 [PATCH v3] close_range.2: Add _GNU_SOURCE and unistd.h to SYNOPSIS Mark Wielaard
2024-02-18 1:09 ` Alejandro Colomar
2024-02-18 12:00 ` Mark Wielaard
2024-02-18 13:08 ` Alejandro Colomar
2024-02-18 14:14 ` G. Branden Robinson [this message]
2024-02-18 15:18 ` man page base paragraph inset/indentation (was: [PATCH v3] close_range.2: Add _GNU_SOURCE and unistd.h to SYNOPSIS) Alejandro Colomar
2024-02-18 16:36 ` groff 1.24 scheduling thoughts (was: man page base paragraph inset/indentation) G. Branden Robinson
2024-02-18 13:15 ` [PATCH v3] close_range.2: Add _GNU_SOURCE and unistd.h to SYNOPSIS Alejandro Colomar
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=20240218141447.q34tghthp7d4llpg@illithid \
--to=g.branden.robinson@gmail.com \
--cc=ahajkova@redhat.com \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mark@klomp.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