From: "John P. Linderman" <jpl.jpl@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: Computer Old Farts Followers <coff@tuhs.org>
Subject: Re: [COFF] Scribe (Typesetting System) and Unix
Date: Thu, 13 Jan 2022 10:08:24 -0500 [thread overview]
Message-ID: <CAC0cEp-ZYZcEU6JbsuP4W_srxycLcLH5GWZxFv4_zf6qsTyVsA@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2NaKgiy3_sD_QziKk1tmAhL+FuHbeTUARkrVEstkKz4aA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 836 bytes --]
On Thu, Jan 13, 2022 at 9:57 AM Clem Cole <clemc@ccc.com> wrote:
> below.... [excellent job -- you wrote what I had planned -- few
> tweeks/color added below].
>
> On Wed, Jan 12, 2022 at 10:31 PM Win Treese <treese@acm.org> wrote:
>
>> Scribe was in the mix after troff and TeX.
>
> Fun fact, I believe that bwk was Brian's thesis committee
>
>
>> Brian Reid’s observation was that writers should be writing, and
>> publishing professionals should design how documents look.
>
>
>>
Many of us who wrote articles for the Bell System Technical Journal would
disagree. The BSTJ publishers could transform something that made sense
when viewed as troff output into unintelligible gibberish. You cannot split
a UNIX command line into multiple lines just because it "looks better".
Sometimes format really matters.
[-- Attachment #1.2: Type: text/html, Size: 2237 bytes --]
[-- Attachment #2: Type: text/plain, Size: 141 bytes --]
_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
next prev parent reply other threads:[~2022-01-13 15:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 2:04 josh
2022-01-13 2:03 ` Greg 'groggy' Lehey
2022-01-13 3:24 ` Win Treese
2022-01-13 14:56 ` Clem Cole
2022-01-13 15:08 ` John P. Linderman [this message]
2022-01-13 16:06 ` Clem Cole
2022-01-13 16:24 ` Warner Losh
2022-01-13 16:39 ` Harald Arnesen
2022-01-13 18:00 ` Bakul Shah
2022-01-13 15:35 ` Dan Cross
2022-01-13 16:02 ` Warner Losh
2022-01-13 16:20 ` Clem Cole
2022-01-13 16:32 ` Warner Losh
2022-01-13 16:42 ` Lars Brinkhoff
2022-01-13 16:52 ` Larry McVoy
2022-01-13 16:54 ` Clem Cole
2022-01-13 17:06 ` Clem Cole
2022-01-13 18:16 ` Dan Cross
2022-01-13 20:00 ` Larry McVoy
2022-01-13 20:26 ` Chet Ramey
2022-01-13 16:13 ` Charles H Sauer
2022-01-13 22:53 ` David Arnold
2022-01-14 1:53 ` Adam Thornton
2022-01-13 3:26 ` Theodore Ts'o
2022-01-13 16:25 ` Larry McVoy
2022-01-13 16:33 ` Dan Cross
2022-01-13 22:19 ` David Arnold
2022-01-13 13:54 ` Adam Sampson
2022-01-13 16:37 ` Lars Brinkhoff
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=CAC0cEp-ZYZcEU6JbsuP4W_srxycLcLH5GWZxFv4_zf6qsTyVsA@mail.gmail.com \
--to=jpl.jpl@gmail.com \
--cc=clemc@ccc.com \
--cc=coff@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).