From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Adam Borowski <kilobyte@angband.pl>, linux-man@vger.kernel.org
Cc: mtk.manpages@gmail.com
Subject: Re: [PATCH 1/3] console_codes.4: \e[21m is now underline
Date: Fri, 7 Feb 2020 16:30:05 +0100 [thread overview]
Message-ID: <d5bdf217-3614-7bf2-afb4-e8b2b400bb51@gmail.com> (raw)
In-Reply-To: <20190308194059.9560-1-kilobyte@angband.pl>
Hello Adam,
On 3/8/19 8:40 PM, Adam Borowski wrote:
> Since 65d9982d7 (4.17), it follows xterm rather than common sense and
> consistency, being the only command 1..9 where N+20 doesn't undo what
> N did. As libvte 0.51.90 got changed the same way, this behaviour will
> probably stay.
>
> Signed-off-by: Adam Borowski <kilobyte@angband.pl>
Thanks. Patch applied.
Cheers,
Michael
> ---
> man4/console_codes.4 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man4/console_codes.4 b/man4/console_codes.4
> index 35f52fc64..d605b058d 100644
> --- a/man4/console_codes.4
> +++ b/man4/console_codes.4
> @@ -258,7 +258,7 @@ The toggle meta flag
> causes the high bit of a byte to be toggled
> before the mapping table translation is done.
> T}
> -21 set normal intensity (ECMA-48 says "doubly underlined")
> +21 set underline (<4.17 and many other terminals set normal intensity)
> 22 set normal intensity
> 24 underline off
> 25 blink off
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next parent reply other threads:[~2020-02-07 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190308194059.9560-1-kilobyte@angband.pl>
2020-02-07 15:30 ` Michael Kerrisk (man-pages) [this message]
[not found] ` <20190308194059.9560-3-kilobyte@angband.pl>
2020-02-07 15:35 ` [PATCH 3/3] console_codes.4: \e[90m to 97, 100 to 107 Michael Kerrisk (man-pages)
[not found] ` <20190308194059.9560-2-kilobyte@angband.pl>
2020-02-07 15:34 ` [PATCH 2/3] console_codes.4: \e[38m and \e[48m Michael Kerrisk (man-pages)
2020-02-07 16:26 ` Michael Kerrisk (man-pages)
2020-02-07 20:07 ` Adam Borowski
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=d5bdf217-3614-7bf2-afb4-e8b2b400bb51@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=kilobyte@angband.pl \
--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;
as well as URLs for NNTP newsgroup(s).