From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] Re: man pages
Date: Tue, 24 Aug 2021 17:34:43 -0400 [thread overview]
Message-ID: <9155B28D30131B29945A1822EEC99D90@eigenstate.org> (raw)
In-Reply-To: <CABB-WO_LUq8oUn1paedBA-5Z2F8Fb2wNEErB01LhaxtFAsfgwg@mail.gmail.com>
Quoth Stuart Morrow <morrow.stuart@gmail.com>:
> I was referring to the first post in the thread, with the 12K attachment.
>
> Those diffs were at that time already a month old and ignored.
>
Thanks for pinging.
So, lots of these look like some bike-shedding
for the sake of bike-shedding, without really
improving the quality of the documentation.
For example, is 'foreign-character-set' really
an improvement over 'foreign character-set'?
Is character-set an improvement over character set?
I think both changes are worse.
On the other hand, there are actual fixes
for omissions, like:
-.B "newdev {low|full|high} \fIport\fP
+.B "newdev {low|full|high|super} \fIport\fP
and styling issues like:
-.I str ,
+.IR str ,
If I could have this without the bikeshedding,
that would have been ideal.
Anyways, I think qwx is looking at this patch,
so I'll let them handle it.
next prev parent reply other threads:[~2021-08-24 22:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABB-WO9mMVTigW9s96s88nPvA8fEijD6m-K_aR-=cMvDG363dQ@mail.gmail.com>
2021-08-14 16:56 ` Stuart Morrow
2021-08-24 17:21 ` Stuart Morrow
2021-08-24 20:27 ` qwx
2021-08-24 21:02 ` Stuart Morrow
2021-08-24 21:09 ` hiro
2021-08-24 21:13 ` Stuart Morrow
2021-08-24 21:33 ` Stuart Morrow
2021-08-24 21:34 ` ori [this message]
2021-08-24 23:42 ` Stuart Morrow
2021-08-25 1:02 ` ori
2021-08-25 12:05 ` Stuart Morrow
2021-08-25 22:50 ` ori
2021-08-26 10:02 ` Stuart Morrow
2021-08-26 14:26 ` ori
2021-08-24 21:49 ` qwx
2021-08-24 21:20 ` Humm
2021-08-25 3:18 ` ori
2021-08-25 9:37 ` hiro
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=9155B28D30131B29945A1822EEC99D90@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.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).