From: qwx <qwx@sciops.net>
To: 9front@9front.org
Subject: Re: [9front] Re: man pages
Date: Tue, 24 Aug 2021 23:49:37 +0200 [thread overview]
Message-ID: <15CD9AD70DBA6E3C24956FD65F4CF2AD@wopr.sciops.net> (raw)
In-Reply-To: <CABB-WO_LUq8oUn1paedBA-5Z2F8Fb2wNEErB01LhaxtFAsfgwg@mail.gmail.com>
I pushed part of your changes. Some I rejected on my own
accord. My earlier point stands, there are many more
instances of UTF and other shit that you didn't touch.
Moreover, if we do this for `UTF', why not `HTML' or `USB'
or whatever?
Thanks for bumping this, and any further changes are
welcome.
> Oh yes, there are. What comes to mind immediately is citation style
> and handling of options in SYNOPSIS (sometimes all are listed and
> sometimes there is just “[options]”), as well as just bad troff.
> There are some checks for bad stuff (see for example `mk punccheck` in
> /sys/man).
>
> --
> Humm
As always, patches welcome.
Thanks,
qwx
next prev parent reply other threads:[~2021-08-24 21: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
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 [this message]
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=15CD9AD70DBA6E3C24956FD65F4CF2AD@wopr.sciops.net \
--to=qwx@sciops.net \
--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).