Linux Manual Pages development
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 3/4] console_codes.4: mention caveats for xterm's ESC ] 50 command
Date: Wed, 8 Jul 2026 17:29:17 +0200	[thread overview]
Message-ID: <ak5sM16sSOxLmWZo@devuan> (raw)
In-Reply-To: <20260708121458.46465-3-jengelh@inai.de>

[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]

Hi Jan,

On 2026-07-08T14:14:57+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>
> ---
>  man/man4/console_codes.4 | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/man/man4/console_codes.4 b/man/man4/console_codes.4
> index 2fa8368e1..e309293ca 100644
> --- a/man/man4/console_codes.4
> +++ b/man/man4/console_codes.4
> @@ -760,7 +760,9 @@ 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[] (normally disabled; cf. the "allowFontOps" resource)

Please replace "cf." by English words.  Also, where is "allowFontOps"
documented?


Cheers,
Alex

> +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 --]

  reply	other threads:[~2026-07-08 15:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08 12:14 [PATCH 1/4] console_codes.4: rephrase description for xterm's ESC ] 4 command Jan Engelhardt
2026-07-08 12:14 ` [PATCH 2/4] console_codes.4: rephrase description for xterm's ESC ] 10 command Jan Engelhardt
2026-07-08 12:14 ` [PATCH 3/4] console_codes.4: mention caveats for xterm's ESC ] 50 command Jan Engelhardt
2026-07-08 15:29   ` Alejandro Colomar [this message]
2026-07-08 19:03     ` Jan Engelhardt
2026-07-10 13:55       ` Alejandro Colomar
2026-07-08 12:14 ` [PATCH 4/4] console_codes.4: document more xterm codes Jan Engelhardt
2026-07-08 15:30   ` Alejandro Colomar
2026-07-08 15:17 ` [PATCH 1/4] console_codes.4: rephrase description for xterm's ESC ] 4 command Alejandro Colomar
2026-07-08 15:24   ` 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=ak5sM16sSOxLmWZo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox