From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: TUHS main list <tuhs@tuhs.org>
Cc: groff@gnu.org
Subject: [TUHS] Re: On the term "justification"
Date: Fri, 28 Jun 2024 14:32:39 -0500 [thread overview]
Message-ID: <20240628193239.enanlphfvmhcn46l@illithid> (raw)
In-Reply-To: <CAKH6PiWHByQGya1yiLiSUxuXB9FPEnE2=Ukh49zaHP9Y3vmRZg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 413 bytes --]
At 2024-06-28T15:19:49-0400, Douglas McIlroy wrote:
> Oops, my last post ascribed Runoff to the 15th century, "sixty
> decades" ago.
That's okay--no one on TUHS saw it unless they're also subscribed to
groff@gnu.
I noticed, but parked my reply for a day to keep the list traffic volume
down.
Also to see if anyone wants to defend how
.ad c
foo\p
.ad
bar\p
.ad r
baz\p
.ad
qux\p
works. ;-)
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-06-28 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 19:19 Douglas McIlroy
2024-06-28 19:32 ` G. Branden Robinson [this message]
2024-06-29 19:35 ` John Levine
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=20240628193239.enanlphfvmhcn46l@illithid \
--to=g.branden.robinson@gmail.com \
--cc=groff@gnu.org \
--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).