From: Alejandro Colomar <alx@kernel.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 1/2] console_codes.4: mention caveats for xterm's ESC ] 50 command
Date: Sat, 18 Jul 2026 14:22:53 +0200 [thread overview]
Message-ID: <altv-loTJXlWxgUf@devuan> (raw)
In-Reply-To: <20260710221035.26529-1-jengelh@inai.de>
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
Hi Jan,
On 2026-07-11T00:10:34+0200, Jan Engelhardt wrote:
> Fonts are only settable if xterm was launched with the right options
> (or X11 resources) that would allow this operation.
>
> Signed-off-by: Jan Engelhardt <jengelh@inai.de>
Thanks! I've applied the patch, with some minor tweaks.
Have a lovely day!
Alex
> ---
> man/man4/console_codes.4 | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/man/man4/console_codes.4 b/man/man4/console_codes.4
> index 2fa8368e1..534510a4b 100644
> --- a/man/man4/console_codes.4
> +++ b/man/man4/console_codes.4
> @@ -760,7 +760,10 @@ Change log file to
> .I name
> (normally disabled by a compile-time option).
> T}
> -ESC ] 50 ; \f[I]fn\f[] ST Set font to \f[I]fn\f[].
> +ESC ] 50 ; \f[I]fn\f[] ST T{
> +Set font to \f[I]fn\f[] (the escape code is normally disabled;
> +consult the xterm manpage for the "allowFontOps" setting)
> +T}
> .TE
> .P
> It recognizes the following with slightly modified meaning
> --
> 2.54.0
>
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-07-18 12:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 22:10 [PATCH 1/2] console_codes.4: mention caveats for xterm's ESC ] 50 command Jan Engelhardt
2026-07-10 22:10 ` [PATCH 2/2] console_codes.4: document more xterm codes Jan Engelhardt
2026-07-18 12:23 ` Alejandro Colomar
2026-07-18 12:22 ` Alejandro Colomar [this message]
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=altv-loTJXlWxgUf@devuan \
--to=alx@kernel.org \
--cc=jengelh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.