From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: Escaping whitespace
Date: Thu, 7 Jan 2021 18:11:35 +0100 [thread overview]
Message-ID: <d5e5fc9f-d283-1457-167b-d2716648656d@gmail.com> (raw)
In-Reply-To: <5058547d-c021-0aa9-4698-667c4917a12b@gmail.com>
Hi Michael,
On 1/6/21 1:51 PM, Michael Kerrisk (man-pages) wrote:
> Hi Alex,
>
> On 1/5/21 10:56 PM, Alejandro Colomar (man-pages) wrote:
>> Hi Michael,
>>
>> While having a look at your latest commits,
>> I saw that there's a bit of inconsistency in escaping whitespace
>> (existing previous to the commit):
>>
>> Sometimes it's [!\ (], and sometimes it's [! (].
>
> Thanks for prodding me about this.
>
> Yes, it's inconsistent. And given the use of .nf/.fi
> around the text blocks, escaping the spaces serves no
> purpose. So I made a more radical fix; see commit
> 5c10d2c5e299011e34adb568737acfc8920fc27c
Nice!
After your following commit (422d5327a88fa89394100bafad69b21e50b26399),
I found that there are many such cases. Just [[grep -rnI '\\ ' man?]]
and you'll see. Some of them are valid, but a lot of them aren't.
What do you want to do about them?
Thanks,
Alex
>
> Thanks,
>
> Michael
>>
>
>
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2021-01-07 17:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 21:56 Escaping whitespace Alejandro Colomar (man-pages)
2021-01-06 12:51 ` Michael Kerrisk (man-pages)
2021-01-07 17:11 ` Alejandro Colomar (man-pages) [this message]
2021-01-08 11:29 ` Michael Kerrisk (man-pages)
2021-01-08 11:49 ` Alejandro Colomar (man-pages)
2021-01-08 12:35 ` Alejandro Colomar (man-pages)
2021-01-08 12:44 ` Michael Kerrisk (man-pages)
2021-01-08 12:57 ` Alejandro Colomar (man-pages)
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=d5e5fc9f-d283-1457-167b-d2716648656d@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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.