From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: nick black <dankamongmen@gmail.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
linux-kernel@vger.kernel.org, linux-man@vger.kernel.org
Subject: Re: [patch] console_codes.4: ffix
Date: Sun, 20 Mar 2022 19:15:02 +0100 [thread overview]
Message-ID: <fd0b3fea-4b40-ffba-442f-00908a5335a9@gmail.com> (raw)
In-Reply-To: <20220320160217.gws42lklp6ishzub@localhost.localdomain>
Hi, nick, and Branden!
On 3/20/22 17:02, G. Branden Robinson wrote:
> Hi Nick,
>
> Alex has been waiting on me for a review of this patch. I took longer
> than I should have because I thought he was expecting a technical
> evaluation of the accuracy of the sequences documented.[1] Now I see it
> was just a matter of man(7) and tbl(1) syntactical and style review.
No, you were originally right. I did mean both, but especially
"a technical evaluation of the accuracy of the sequences documented".
You did it anyway, so thanks! :)
>
> Easy bits first.
>
>> Remove CSI prefix from the list of non-CSI escapes.
>
> +1
>
>> End all items of said list with periods, matching other sections of
>> the page.
>
> +1
>
>> Fix up the busted OSC command list (reset palette and set palette).
>
>> ESC ] OSC T{
>> -(Should be: Operating system command)
>> -ESC ] P \fInrrggbb\fP: set palette, with parameter
>> -given in 7 hexadecimal digits after the final P :-(.
>> -Here \fIn\fP is the color (0\(en15), and \fIrrggbb\fP indicates
>> +Operating System Command prefix.
>> +T}
>> +ESC ] R Reset palette.
>> +ESC ] P T{
>> +Set palette, with parameter given in 7 hexadecimal digits \fInrrggbb\fP after
>> +the final P. Here \fIn\fP is the color (0\(en15), and \fIrrggbb\fP indicates
>> the red/green/blue values (0\(en255).
>> -ESC ] R: reset palette
>> T}
>
> Yes, this was majorly hosed up, syntactically. What you have is good
> repair to obvious damage. +1.
>
> I have some suggestions for further improvement, but please don't gate
> the patch application on these.
[...]
Okay, thanks!
nick, can you please resend the patch? I've lost the original email.
Cheers,
Alex
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2022-03-20 18:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 6:48 [patch] console_codes.4: ffix nick black
2022-01-17 17:30 ` Alejandro Colomar (man-pages)
2022-01-19 17:05 ` nick black
2022-01-25 17:35 ` nick black
[not found] ` <CAN4uE+p-uKzHNYry2YhCMfEFBQ2jUqpDAGx=+eha01w-L4fAjg@mail.gmail.com>
2022-03-20 16:02 ` G. Branden Robinson
2022-03-20 18:15 ` Alejandro Colomar (man-pages) [this message]
2022-03-21 8:30 ` nick black
2022-03-22 12:27 ` Alejandro Colomar (man-pages)
2022-03-22 12:56 ` nick black
2022-03-22 12:59 ` Alejandro Colomar (man-pages)
2022-03-22 13:01 ` nick black
2022-03-21 8:33 ` nick black
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=fd0b3fea-4b40-ffba-442f-00908a5335a9@gmail.com \
--to=alx.manpages@gmail.com \
--cc=dankamongmen@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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