From: Alejandro Colomar <alx@kernel.org>
To: Jan Engelhardt <ej@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: Fri, 10 Jul 2026 15:55:30 +0200 [thread overview]
Message-ID: <alD15mDndM01rrNu@devuan> (raw)
In-Reply-To: <4qn8ns3s-44n1-r357-q351-r5p6pr15oq90@vanv.qr>
[-- Attachment #1: Type: text/plain, Size: 2090 bytes --]
Hi Jan,
On 2026-07-08T21:03:01+0200, Jan Engelhardt wrote:
>
> On Wednesday 2026-07-08 17:29, Alejandro Colomar wrote:
> >>
> >> -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.
>
> But I was just following precedent:
>
> man-pages$ git grep '\be\.g\.'|wc -l
> 481
> $ git grep '\bi\.e\.'|wc -l
> 516
> $ git grep '\bcf\.'|wc -l
> 10
> $ git grep '\bN\.?B\.'|wc -l
> 0
There are still some uses, but we're trying to reduce them (and
especially, not add more). See man-pages(7):
$ MANWIDTH=72 man man-pages | awk '/Use of e.g.,/,/^$/'
Use of e.g., i.e., etc., a.k.a., and similar
In general, the use of abbreviations such as "e.g.", "i.e.",
"etc.", "cf.", and "a.k.a." should be avoided, in favor of suit‐
able full wordings ("for example", "that is", "and so on", "com‐
pare to", "also known as").
Compare the numbers with:
$ grep -rio for.example man/ | wc -l
585
$ grep -rio that.is man/ | wc -l
808
$ grep -rio compare.to | wc -l
2
> and the Linux kernel source for completeness:
>
> $ git grep '\be\.g\.'|wc -l
> 9582
> $ git grep '\bi\.e\.'|wc -l
> 7397
> $ git grep '\bN\.?B\.'|wc -l
> 235
> $ git grep '\bcf\.'|wc -l
> 165
>
>
> >Also, where is "allowFontOps" documented?
>
> The console_codes.4 manpage section that is being edited talks
> extensively about *xterm*, so it felt obvious that, if a term was
> unclear, the reader need look no further than into the xterm manpage
> to resolve his quest.
Hmmm, I'd append something like "in xterm(1)". It's not much text, and
helps know where to search for its documentation. wdyt?
Have a lovely day!
Alex
> In fact, the xterm manpage even declares what constitutes "dynamic"
> colors (now that I happen to look for that term which tripped me up
> earlier).
>
> Does that sound reasonable?
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-07-10 13:55 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
2026-07-08 19:03 ` Jan Engelhardt
2026-07-10 13:55 ` Alejandro Colomar [this message]
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=alD15mDndM01rrNu@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 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.