From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: custom NS and NE man(7) macros
Date: Tue, 26 Sep 2023 08:58:31 -0500 [thread overview]
Message-ID: <20230926135831.35ljg4emxie4adl4@illithid> (raw)
In-Reply-To: <CAKH6PiVOMLOYf_MCaWkXsudqMemaBfQQnDhhfjPqWTCz58msew@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
Hi Doug,
At 2023-09-26T09:38:07-0400, Douglas McIlroy wrote:
> > You didn't say, but I reckon this is a survey of man(7) macros that
> > might be considered extensions?
>
> My presentation was too cute for my own good. I pointed out the
> consistency of xS/xE for various x.
Oh!
> I apologized for EX/EE, which varied from that form
It seems then that we are owed an apology from other quarters for
`EQ`/`EN`. ;-)
> (as UR/UE did more recently),
There is also `MT`/`ME`, another groff 1.20 extension.
> and I questioned OQ/CQ, which utterly breaks it.
I proposed `QO`/`QC`, but yes, the same is true of that letter ordering.
> The intended point was that one should have a strong rationale
> for deviating from established custom, and thereby fostering
> mental overload.
Fair. I'm fine with renaming my proposed quotation macros `QS`/`QE`.
Something I'm still mulling over is how one would specify to these new
macros that they should not perform a break. Or maybe they should
perform no break by default. That would seem to be the more common
expected case.
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-09-26 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 13:38 Douglas McIlroy
2023-09-26 13:58 ` G. Branden Robinson [this message]
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=20230926135831.35ljg4emxie4adl4@illithid \
--to=g.branden.robinson@gmail.com \
--cc=douglas.mcilroy@dartmouth.edu \
--cc=tuhs@tuhs.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).