Linux Manual Pages development
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Jeff Layton <jlayton@kernel.org>, Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH man-pages] man/man2const: document the new F_SETDELEG and F_GETDELEG constants
Date: Tue, 13 Jan 2026 09:05:10 -0600	[thread overview]
Message-ID: <20260113150510.74mmegkp46dmd5uv@illithid> (raw)
In-Reply-To: <14e88ee6ff3ffd671f579d103c53ebe98b4f92e2.camel@kernel.org>

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

Hi Jeff and Alex,

At 2026-01-13T09:45:11-0500, Jeff Layton wrote:
> On Tue, 2026-01-13 at 15:13 +0100, Alejandro Colomar wrote:
> > On Mon, Jan 12, 2026 at 01:47:11PM -0500, Jeff Layton wrote:
[...]
> > > +.br
> > 
> > This .br seems superfluous.
> > 
> 
> You would think, no? But when I remove it, man seems to stick both
> lines togther. I really do not grok groff at all.

Try the introduction in groff_man_style(7).

https://man7.org/linux/man-pages/man7/groff_man_style.7.html

> I'm happy to accept other suggestions on how to fix that though.

Here's the hunk with context:

+.EE
+.P
+.BI "int fcntl(int " fd ", F_SETDELEG, struct delegation *" deleg );
+.br
+.BI "int fcntl(int " fd ", F_GETDELEG, struct delegation *" deleg );
+.fi

The `br` request really is necessary there, as Jeff says.  This is an
ordinary paragraph.  The `EE` (end example) restores filling.  So you
_do_ need the `br` request here _but_ you can discard the `fi` request
to enable filling afterward, because it's already on.

An alternative will become available in groff 1.24.0; you'll be able to
use groff man's syopsis macros to set C function protoypes.

https://cgit.git.savannah.gnu.org/cgit/groff.git/tree/NEWS?id=cfcfe1dde5b1752484dcd94dde1d65c65a5540fb#n409

Regards,
Branden

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

  reply	other threads:[~2026-01-13 15:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12 18:47 [PATCH man-pages] man/man2const: document the new F_SETDELEG and F_GETDELEG constants Jeff Layton
2026-01-13 14:13 ` Alejandro Colomar
2026-01-13 14:45   ` Jeff Layton
2026-01-13 15:05     ` G. Branden Robinson [this message]
2026-01-13 15:12     ` 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=20260113150510.74mmegkp46dmd5uv@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=alx@kernel.org \
    --cc=jlayton@kernel.org \
    --cc=linux-fsdevel@vger.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