From: nick black <dankamongmen@gmail.com>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org,
Michael Kerrisk <mtk.manpages@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] console_codes.4: ffix
Date: Tue, 25 Jan 2022 12:35:43 -0500 [thread overview]
Message-ID: <YfA07xh8an0c4AIt@schwarzgerat.orthanc> (raw)
In-Reply-To: <YehE3p7es9/4wBuM@schwarzgerat.orthanc>
nick black left as an exercise for the reader:
> if we're going to keep it, we ought add OSC to this section by
> the same reasoning. i can do that and send a fresh patch, or you
> can do it to my patch, or we can do with what i have.
...
> sequence, especially since there's really no user-relevant
> reason as to why one is in any given group. but i can go ahead
> and break this section out if you'd like.
...
> put another way, some people might read the man page wanting to
> know "how do i change a color". i can't imagine anyone ever
> wanting to know "what are the various OSC-prefixed commands?"
> that said, i'm happy to introduce the substructure if it gets
> the formatting fixed =].
Alejandro, would you like me to make some/all of the mentioned
changes, or is this patch fine as it is, or will you be making
the changes? Right now the console_codes(4) page has nasty
formatting errors (addressed herein); even if we make no content
changes, they should be fixed IMHO.
--
nick black -=- https://www.nick-black.com
to make an apple pie from scratch,
you need first invent a universe.
next prev parent reply other threads:[~2022-01-25 17:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 6:48 [patch] console_codes.4: ffix nick black
2022-01-17 17:30 ` Alejandro Colomar (man-pages)
2022-01-19 17:05 ` nick black
2022-01-25 17:35 ` nick black [this message]
[not found] ` <CAN4uE+p-uKzHNYry2YhCMfEFBQ2jUqpDAGx=+eha01w-L4fAjg@mail.gmail.com>
2022-03-20 16:02 ` G. Branden Robinson
2022-03-20 18:15 ` Alejandro Colomar (man-pages)
2022-03-21 8:30 ` nick black
2022-03-22 12:27 ` Alejandro Colomar (man-pages)
2022-03-22 12:56 ` nick black
2022-03-22 12:59 ` Alejandro Colomar (man-pages)
2022-03-22 13:01 ` nick black
2022-03-21 8:33 ` nick black
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=YfA07xh8an0c4AIt@schwarzgerat.orthanc \
--to=dankamongmen@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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).