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: URIs mark-up
Date: Fri, 8 Jan 2021 14:01:57 +0100 [thread overview]
Message-ID: <94ec3af1-ecfa-88c8-f6ce-19771cf83ef4@gmail.com> (raw)
In-Reply-To: <c9a74529-7d00-afef-4a91-603da19300d4@gmail.com>
Hi Michael,
On 1/8/21 1:57 PM, Michael Kerrisk (man-pages) wrote:
> Hi Alex,
>
> The obligatory:
>
> [[
> Because it messes up the order in which people normally read text.
> > Why is top-posting such a bad thing?
> >> Top-posting.
> >>> What is the most annoying thing in e-mail?
> ]]
>
> [Rearranged]
Oops! :-)
>
>> On 1/8/21 12:00 PM, Michael Kerrisk (man-pages) wrote:
>>> Hi Alex,
>>>
>>> On 1/7/21 6:50 PM, Alejandro Colomar (man-pages) wrote:
>>>> Hi Michael,
>>>>
>>>> See hostname.7:102.
>>>> There are URLs and they're not marked up in any way.
>>>> I guess there are a lot more like those around the pages.
>>>> Should they?
>>>
>>> I'm not sure what you mean by "not marked up". That
>>> URI is wrapped in a .UR/.UE pair, and I think all of
>>> the others in other pages are too(?).
>>
>> I meant the (fake) URLs around line 102.
>> And yes, I meant surrounded by .UR/.UE, which they're not.
>> But maybe it's exactly because they're fake?
>
> Oh -- sorry, I misunderstood which line you meant. I
> think maybe yes, because they are fake.
Okay
Thanks,
Alex
>
> Thanks,
>
> Michael
>
>
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
prev parent reply other threads:[~2021-01-08 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 17:50 URIs mark-up Alejandro Colomar (man-pages)
2021-01-08 11:00 ` Michael Kerrisk (man-pages)
2021-01-08 11:10 ` Alejandro Colomar (man-pages)
2021-01-08 12:57 ` Michael Kerrisk (man-pages)
2021-01-08 13:01 ` Alejandro Colomar (man-pages) [this message]
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=94ec3af1-ecfa-88c8-f6ce-19771cf83ef4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox