[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2] man*/: ffix (migrate to `MR`)
From: |
Alejandro Colomar |
Subject: |
Re: [PATCH v2] man*/: ffix (migrate to `MR`) |
Date: |
Wed, 16 Aug 2023 14:12:21 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.1 |
Hi Branden,
On 2023-08-16 05:55, G. Branden Robinson wrote:
[...]
>> Would you mind sending an updated commit message?
>
> I did, but you found a fresh problem, this time with part 1, so I guess
> we'll be going to v4! :-O Also I'm going to make an attempt to drive
> the part 1 change with sed as well. Just to see if I can, and to see
> what happens.
Great! (As long as it's kept as a separate patch. ;)
>
>> Heh, I noticed some weirdness about it, but it happened to be after a
>> -rCHECKSTYLE, so it seemed like it could be some improvements that you
>> had applied upstream to CHECKSTYLE. =3 definitely made sense to that
>> register.
>
> GNU troff(1) does not raise a diagnostic if a register assignment is
> followed by garbage. That's disappointing.
>
> Filed. https://savannah.gnu.org/bugs/?64559
Nice.
>
>>> Please double-check for that before pushing to kernel.org.
>>
>> Please send one that I don't need to modify. I don't like modifying
>> other's stuff, in case I break it. :)
>
> Did v3 2/2 show up for you without quoted-printable damage?
Yup. I assume Thunderbird is not messing with the source of
the received email. I bet it's neomutt(1), even if I'd expect
it's not the kind of program that would do that.
Please send a hand-crafted encrypted copy in an attached file,
where no program can mess with it.
>
>>>>>> and against man-pages(7) recommendations.
>>>>
>>>> Well, we should update those to use MR.
>>>
>>> And man(7) too, I guess. What do you think?
>>
>> I want to kill that page. Please have a look at it, take anything
>> good that it has for groff_man{,_style}(7), and ping me when I
>> should sharpen the scythe. ;)
>
> Ok, will do.
>
> If the page is withdrawn, I expect distributors will need to manage the
> man.7 page using Debian's "alternatives" mechanism or similar; if
> groff_man.7 is installed, man.7 should be a symlink to it. If
> mandoc_man.7 is installed, likewise. If both are installed, the
> distributor needs to select a default preference.
>
> I expect you will want to emphasize this in the release announcement,
> when the time comes.
Sure. 6.6 will be a big release. Maybe there are many bug-fix patches
to it... like 6?
>
> This already needs to happen with soelim(1) and roff(7), but it doesn't,
> exactly; Debian renames mandoc's versions of the former to msoelim(1)
> and the latter to mandoc_roff(1). Termux simply throws groff's versions
> away and installs mandoc's versions as soelim(1) and roff(7).
>
> I also use Termux.
This reminds me I need to ping for the replacement of my Linux phone,
which has issues, and I can't receive calls. :|
> Imagine my surprise when I upgraded to groff 1.23.0
> on my tablet and brought up roff(7). I was expecting to see myself in
> the mirror, and what should greet me but the visage of Ingo Schwarze!
Huh! Under what criteria do they choose mandoc_roff(7) as /the/ roff(7)?
>
> Unnerving, no?
It is!
Cheers,
Alex
>
> Regards,
> Branden
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
OpenPGP_signature
Description: OpenPGP digital signature