From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man <linux-man@vger.kernel.org>
Subject: Re: URIs mark-up
Date: Fri, 8 Jan 2021 13:57:48 +0100 [thread overview]
Message-ID: <c9a74529-7d00-afef-4a91-603da19300d4@gmail.com> (raw)
In-Reply-To: <47d7e64c-16a2-e935-de14-0c320510e382@gmail.com>
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]
> 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.
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2021-01-08 12:58 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) [this message]
2021-01-08 13:01 ` 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=c9a74529-7d00-afef-4a91-603da19300d4@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=alx.manpages@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 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.