From: James Cloos <cloos@jhcloos.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Joey Hess <id@joeyh.name>, groff@gnu.org, linux-man@vger.kernel.org
Subject: Re: on "bricktext"
Date: Mon, 02 Jun 2025 03:16:12 -0400 [thread overview]
Message-ID: <m3bjr6obpf.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <20250602064936.wrizwxkcdpx4btpq@illithid>
>>>>> "BR" == G Branden Robinson <g.branden.robinson@gmail.com> writes:
BR> I found an exhibit of bricktext from 1998.
BR> https://lists.debian.org/debian-devel/1998/10/msg02449.html
didn't we all do a instance or three of that back in the day?
ie adjust some words here and there to arrange justification?
-JimC
--
James Cloos <cloos@jhcloos.com>
OpenPGP: https://jhcloos.com/0x997A9F17ED7DAEA6.asc
prev parent reply other threads:[~2025-06-02 7:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 10:56 Paragraphs formatted differently depending on previous ones Alejandro Colomar
2025-05-02 12:01 ` G. Branden Robinson
2025-05-02 12:26 ` grof --run Alejandro Colomar
2025-05-02 14:19 ` G. Branden Robinson
2025-05-02 14:59 ` Alejandro Colomar
2025-05-03 0:49 ` G. Branden Robinson
2025-05-03 7:25 ` Alejandro Colomar
2025-05-05 10:50 ` Colin Watson
2025-05-05 15:41 ` Ingo Schwarze
2025-05-07 18:10 ` G. Branden Robinson
2025-05-02 12:42 ` Paragraphs formatted differently depending on previous ones Alejandro Colomar
2025-05-02 14:29 ` G. Branden Robinson
2025-05-02 15:30 ` Alejandro Colomar
2025-05-02 13:06 ` Martin Lemaire
2025-05-02 14:51 ` G. Branden Robinson
2025-05-02 15:34 ` Alejandro Colomar
2025-05-03 1:30 ` G. Branden Robinson
2025-05-02 17:42 ` Dave Kemper
2025-05-02 18:46 ` Martin Lemaire
2025-05-03 0:14 ` G. Branden Robinson
2025-05-05 16:00 ` Joey Hess
2025-06-02 6:49 ` on "bricktext" (was: Paragraphs formatted differently depending on previous ones) G. Branden Robinson
2025-06-02 7:16 ` James Cloos [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=m3bjr6obpf.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=g.branden.robinson@gmail.com \
--cc=groff@gnu.org \
--cc=id@joeyh.name \
--cc=linux-man@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.