From: Alejandro Colomar <alx@kernel.org>
To: Jan Engelhardt <ej@inai.de>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v3 2/2] console_codes.4: document more xterm codes
Date: Wed, 8 Jul 2026 14:02:22 +0200 [thread overview]
Message-ID: <ak47_pq0BTsoSw0P@devuan> (raw)
In-Reply-To: <p87sp316-232n-8303-q91n-o385066pr74r@vanv.qr>
[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]
Hi Jan,
On 2026-07-08T13:58:04+0200, Jan Engelhardt wrote:
>
> On Wednesday 2026-07-08 13:17, Alejandro Colomar wrote:
>
> >> ESC ] 1 ; \f[I]txt\f[] ST Set icon name to \f[I]txt\f[].
> >> ESC ] 2 ; \f[I]txt\f[] ST Set window title to \f[I]txt\f[].
> >> -ESC ] 4 ; \f[I]num\f[] ; \f[I]txt\f[] ST Set ANSI color \f[I]num\f[] to \f[I]txt\f[].
> >> -ESC ] 10 ; \f[I]txt\f[] ST Set dynamic text color to \f[I]txt\f[].
> >> +ESC ] 4 ; \f[I]num\f[] ; \f[I]txt\f[] ST Set color \f[I]num\f[] (0-255) to \f[I]txt\f[].
> >
> >This seems to reword the description of ESC]4;num;txt, which doesn't
> >seem to match the commit message. Should this go into a separate
> >commit?
>
> I had inspected the xterm source code to figure out what codes are available
> and what they really do. This naturally led to rewording inaccurate
> descriptions in console_codes. I do not think it is necessary to split this
> into much more commits. I could might have written
>
> console_codes.4: document more xterm codes and fix some behavioral descriptions
>
> but that gets a little long for a summary line, wdyt?
I prefer a couple of commits. One commit fixing existing descriptions
and another one adding new ones. Two commits should be enough. That
makes the diff nicer.
Cheers,
Alex
>
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-07-08 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 10:42 [PATCH v3 1/2] console_codes.4: align spacing aids in escape codes Jan Engelhardt
2026-07-08 10:42 ` [PATCH v3 2/2] console_codes.4: document more xterm codes Jan Engelhardt
2026-07-08 11:17 ` Alejandro Colomar
2026-07-08 11:58 ` Jan Engelhardt
2026-07-08 12:02 ` Alejandro Colomar [this message]
2026-07-08 11:14 ` [PATCH v3 1/2] console_codes.4: align spacing aids in escape codes Alejandro Colomar
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=ak47_pq0BTsoSw0P@devuan \
--to=alx@kernel.org \
--cc=ej@inai.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox