From: Alejandro Colomar <alx.mailinglists@gmail.com>
To: Jakub Wilk <jwilk@jwilk.net>, Alejandro Colomar <alx.manpages@gmail.com>
Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
linux-man@vger.kernel.org
Subject: Re: [PATCH] posix.py: ffix: Correctly format URIs
Date: Thu, 21 Jan 2021 21:19:44 +0100 [thread overview]
Message-ID: <68986498-b493-adfc-e66e-1cf791d901b3@gmail.com> (raw)
In-Reply-To: <20210121201426.b6wfycjdegxce7fw@jwilk.net>
On 1/21/21 9:14 PM, Jakub Wilk wrote:
[...]
>>
>> So... does it mean there's a bug in .UR/.UE?
>
> Or a bug in Branden. ;-)>
> Contrary to what he wrote, and what I parroted, .UR/.UE use U+27E8 and
> U+27E9 as delimiters.
>
Ahh, that's it!
Will have to patch it... :-P
next prev parent reply other threads:[~2021-01-21 20:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 19:58 [PATCH] posix.py: ffix: Correctly format URIs Alejandro Colomar
2021-01-09 21:07 ` Alejandro Colomar (man-pages)
2021-01-10 6:50 ` G. Branden Robinson
2021-01-10 14:35 ` Alejandro Colomar (man-pages)
2021-01-10 14:57 ` [PATCH v2] " Alejandro Colomar
2021-01-19 19:59 ` Ping: " Alejandro Colomar (man-pages)
2021-01-20 8:50 ` Michael Kerrisk (man-pages)
2021-01-20 8:55 ` Michael Kerrisk (man-pages)
2021-01-12 20:51 ` [PATCH] " Jakub Wilk
2021-01-14 7:11 ` G. Branden Robinson
2021-01-21 19:54 ` Alejandro Colomar (man-pages)
2021-01-21 20:14 ` Jakub Wilk
2021-01-21 20:19 ` Alejandro Colomar [this message]
2021-01-22 3:23 ` G. Branden Robinson
2021-01-22 9:35 ` Jakub Wilk
2021-01-22 10:07 ` G. Branden Robinson
2021-01-22 10:50 ` Alejandro Colomar (man-pages)
2021-01-22 14:51 ` G. Branden Robinson
2021-01-22 17:27 ` Alejandro Colomar (man-pages)
2021-01-09 22:09 ` Alejandro Colomar (man-pages)
2021-01-22 12:37 ` Ping: " Alejandro Colomar (man-pages)
2021-01-22 15:13 ` Michael Kerrisk (man-pages)
2021-01-22 18:19 ` Alejandro Colomar (man-pages)
2021-01-23 9:15 ` Michael Kerrisk (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=68986498-b493-adfc-e66e-1cf791d901b3@gmail.com \
--to=alx.mailinglists@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=jwilk@jwilk.net \
--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