From: Alejandro Colomar <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>, enh <enh@google.com>
Subject: Re: italicizing pointer stars (was: [PATCH] getline.3: wfix.)
Date: Fri, 5 Aug 2022 23:56:45 +0200 [thread overview]
Message-ID: <e7f43a89-42ce-9bfa-d2fc-3be477330208@gmail.com> (raw)
In-Reply-To: <20220805214949.jsdjstxsftk6mw75@illithid>
[-- Attachment #1.1: Type: text/plain, Size: 885 bytes --]
Hi Branden,
On 8/5/22 23:49, G. Branden Robinson wrote:
>> And the deep rationale why I would like to avoid having the star in a
>> different font is that it could be confused with the glob-like
>> expressions that we use for example to refer to SYS_* macros.
>
> That makes sense. I think instead of adopting glob syntax, I would use
> quotation, but quotation in man(7) is so awkward that many people act
> like it's unavailable. This is just one of many reasons I think man(7)
> should have a `Q` macro to facilitate it.
What do you mean by quotation? How would you transform the following
(taken from clone(2)):
#include <sys/syscall.h> /* Definition of SYS_* constants */
>
>> Did I dodge the bullet?
>
> I think so. :)
:)
Cheers,
Alex
>
> Regards,
> Branden
--
Alejandro Colomar
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-08-05 21:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 20:22 [PATCH] getline.3: wfix enh
2022-07-29 20:52 ` G. Branden Robinson
2022-07-29 20:55 ` enh
2022-08-01 12:53 ` Alejandro Colomar
2022-08-02 21:17 ` enh
2022-08-05 19:20 ` italicizing pointer stars (was: [PATCH] getline.3: wfix.) G. Branden Robinson
2022-08-05 19:40 ` Alejandro Colomar
2022-08-05 21:49 ` G. Branden Robinson
2022-08-05 21:56 ` Alejandro Colomar [this message]
2022-08-15 21:16 ` [PATCH] getline.3: wfix 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=e7f43a89-42ce-9bfa-d2fc-3be477330208@gmail.com \
--to=alx.manpages@gmail.com \
--cc=enh@google.com \
--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