From: Ingo Schwarze <schwarze@usta.de>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: g.branden.robinson@gmail.com, linux-man@vger.kernel.org, groff@gnu.org
Subject: Re: [PATCH 4/6] xattr.7: wfix
Date: Thu, 11 Aug 2022 14:48:51 +0200 [thread overview]
Message-ID: <YvT6s2Sv+M2bEldp@asta-kit.de> (raw)
In-Reply-To: <8edd0272-0c43-b5e7-9220-20094bb5ae23@gmail.com>
Hi Alejandro,
Alejandro Colomar wrote on Mon, Aug 01, 2022 at 03:28:03PM +0200:
> I'd like to arrive to some consensus on usage of \~ and '\ '.
In manual pages, always use "\ " and never use "\~", period.
The former is portable and the latter is a GNU extension.
> What do you think?
I think you are massively overthinking this and the whole SI
argument is irrelevent for manual pages. While the above concern
about robustness is minor, too (both groff and mandoc support \~),
portability is still significantly more important than such minute
typographical details.
Yours,
Ingo
next prev parent reply other threads:[~2022-08-11 12:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 11:45 [PATCH 4/6] xattr.7: wfix Štěpán Němec
2022-07-29 20:58 ` G. Branden Robinson
2022-07-30 14:15 ` Štěpán Němec
2022-07-30 17:53 ` Alejandro Colomar (man-pages)
2022-07-30 17:59 ` Alejandro Colomar (man-pages)
2022-08-01 13:28 ` Alejandro Colomar
2022-08-11 12:48 ` Ingo Schwarze [this message]
2022-08-11 20:17 ` G. Branden Robinson
2022-08-12 14:30 ` Ingo Schwarze
2022-08-12 22:10 ` *roff `\~` support (was: [PATCH 4/6] xattr.7: wfix) G. Branden Robinson
2022-08-13 4:23 ` G. Branden Robinson
2022-08-14 14:15 ` Ingo Schwarze
2022-08-14 22:21 ` G. Branden Robinson
2022-08-13 17:27 ` DJ Chase
2022-08-14 13:56 ` Standardize roff (was: *roff `\~` support) Ingo Schwarze
2022-08-14 14:49 ` DJ Chase
2022-08-14 16:32 ` Alejandro Colomar
2022-08-14 19:43 ` DJ Chase
2022-08-15 11:59 ` Alejandro Colomar
2022-08-16 11:48 ` Ingo Schwarze
2022-08-14 22:35 ` G. Branden Robinson
2022-08-14 22:58 ` DJ Chase
2022-08-15 0:20 ` Sam Varshavchik
2022-08-16 12:52 ` Standardize roff Ingo Schwarze
2022-08-16 23:46 ` Sam Varshavchik
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=YvT6s2Sv+M2bEldp@asta-kit.de \
--to=schwarze@usta.de \
--cc=alx.manpages@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=groff@gnu.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 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.