From: Collin Funk <collin.funk1@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
linux-man@vger.kernel.org
Subject: Re: [PATCH] man/man3/getopt.3: Restore angle brackets.
Date: Wed, 26 Nov 2025 22:54:59 -0800 [thread overview]
Message-ID: <87h5ughsn0.fsf@gmail.com> (raw)
In-Reply-To: <i526ocx5oztrostv55e77cq4fjsdet3g6hf4hej5q5wyyheyrt@eyz2knpjir55>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
Alejandro Colomar <alx@kernel.org> writes:
> On Tue, Nov 25, 2025 at 08:05:24PM -0600, G. Branden Robinson wrote:
>> Hi Collin,
>>
>> At 2025-11-25T17:15:39-0800, Collin Funk wrote:
>> > While looking at 'man -S 3 getopt' the underlining under PID looked
>> > strange to me.
>
> The underlining under 'PID' means that it's a variable part. We use
> that syntax in many pages. This is documented in groff_man(3), as
> Branden said.
>
> However, you might have also noticed some dotted underline that extends
> until the end of the line. I think that's a bug somewhere --might be in
> the terminal emulator, because I see it in xfce4-terminal(1) but not in
> xterm(1)--.
I was using Gnome terminal and Emacs '(man "getopt.3")'.
>> > -.BI _ PID _GNU_nonoption_argv_flags_
>> > +.IR _ PID _GNU_nonoption_argv_flags_
>
> For now, I'll keep the current style, which is consistent in the
> project.
It still looks strange to me. But I guess I will survive. :)
Thank you both for the explanations.
Collin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2025-11-27 6:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 1:15 [PATCH] man/man3/getopt.3: Restore angle brackets Collin Funk
2025-11-26 2:05 ` G. Branden Robinson
2025-11-26 11:57 ` Alejandro Colomar
2025-11-27 6:54 ` Collin Funk [this message]
2025-11-27 12:12 ` Alejandro Colomar
2025-12-19 16:25 ` G. Branden Robinson
2025-12-19 16:33 ` 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=87h5ughsn0.fsf@gmail.com \
--to=collin.funk1@gmail.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.