From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: nick black <dankamongmen@gmail.com>
Cc: "G. Branden Robinson" <g.branden.robinson@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: Tue, 22 Mar 2022 13:27:39 +0100 [thread overview]
Message-ID: <809c40c4-068b-8296-57d9-024e6623362d@gmail.com> (raw)
In-Reply-To: <Yjg3jXCAsjQVHJAi@schwarzgerat.orthanc>
Hi nick,
On 3/21/22 09:30, nick black wrote:
> Alejandro Colomar (man-pages) left as an exercise for the reader:
>> nick, can you please resend the patch? I've lost the original email.
>
> Fix up the busted OSC command list (reset palette and
> set palette). Remove CSI prefix from the list of non-CSI
> escapes. End all items of said list with periods,
> matching other sections of the page.
>
> Signed-off-by: nick black <nickblack@linux.com>
Patch applied.
However, it's weird: I had to apply the following to your patch before
applying it with `git am`:
/^diff --git/s, man4, a/man4,
/^diff --git/s, man4, b/man4,
/^--- man4/s, man4, a/man4,
/^+++ man4/s, man4, b/man4,
I'm curious, how did you generate the patch?
Cheers,
Alex
> ---
> man4/console_codes.4 | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
>
> diff --git man4/console_codes.4 man4/console_codes.4
> index d549b76a9..001de1955 100644
> --- man4/console_codes.4
> +++ man4/console_codes.4
> @@ -139,29 +139,28 @@ T}
> ESC 8 DECRC T{
> Restore state most recently saved by ESC 7.
> T}
> -ESC [ CSI Control sequence introducer
> ESC % Start sequence selecting character set
> ESC % @ \0\0\0Select default (ISO 646 / ISO 8859-1)
> ESC % G \0\0\0Select UTF-8
> ESC % 8 \0\0\0Select UTF-8 (obsolete)
> ESC # 8 DECALN T{
> -DEC screen alignment test \- fill screen with E's
> +DEC screen alignment test \- fill screen with E's.
> T}
> ESC ( T{
> Start sequence defining G0 character set
> (followed by one of B, 0, U, K, as below)
> T}
> ESC ( B T{
> -Select default (ISO 8859-1 mapping)
> +Select default (ISO 8859-1 mapping).
> T}
> ESC ( 0 T{
> -Select VT100 graphics mapping
> +Select VT100 graphics mapping.
> T}
> ESC ( U T{
> -Select null mapping \- straight to character ROM
> +Select null mapping \- straight to character ROM.
> T}
> ESC ( K T{
> -Select user mapping \- the map that is loaded by the utility \fBmapscrn\fP(8)
> +Select user mapping \- the map that is loaded by the utility \fBmapscrn\fP(8).
> T}
> ESC ) T{
> Start sequence defining G1 (followed by one of B, 0, U, K, as above).
> @@ -169,12 +168,13 @@ T}
> ESC > DECPNM Set numeric keypad mode
> ESC = DECPAM Set application keypad mode
> 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}
> .TE
> .ad
--
Alejandro Colomar
Linux man-pages comaintainer; http://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2022-03-22 12:27 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)
2022-03-21 8:30 ` nick black
2022-03-22 12:27 ` Alejandro Colomar (man-pages) [this message]
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=809c40c4-068b-8296-57d9-024e6623362d@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;
as well as URLs for NNTP newsgroup(s).