From: Greg 'groggy' Lehey <grog@lemis.com>
To: josh <joshnatis0@gmail.com>
Cc: coff@tuhs.org
Subject: Re: [COFF] Scribe (Typesetting System) and Unix
Date: Thu, 13 Jan 2022 13:03:14 +1100 [thread overview]
Message-ID: <20220113020314.GN61872@eureka.lemis.com> (raw)
In-Reply-To: <CAFZukdTCh5+F06Lv5avaq5roV0P0iuiUG=FYcA544TEjKYnscg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1128 bytes --]
On Wednesday, 12 January 2022 at 21:04:32 -0500, josh wrote:
> Hi all,
>
> Given the recent (awesome) discussions about the history of *roff and TeX, I
> thought I'd ask about where Brian Reid's Scribe system fits in with all this.
> His thesis is available online here:
> http://reports-archive.adm.cs.cmu.edu/anon/scan/CMU-CS-81-100.pdf, and in my
> opinion is very interesting (also cites papers on roff and TeX). Does anybody
> know if Scribe was ever used on Unix systems? Does it exist at all
> today?
That brings back memories, not of Scribe, but of Scribble by (I think)
Craig Finseth of Mark of the Unicorn, who also wrote the MINCE (MINCE
Is Not Complete Emacs) editor. This would have been round 1980.
Scribble was the first serious text formatting program that I used,
and I quite liked it. I can't recall how it compares to more
mainstream systems.
Greg
--
Sent from my desktop computer.
Finger grog@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 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 2:09 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 [this message]
2022-01-13 3:24 ` Win Treese
2022-01-13 14:56 ` Clem Cole
2022-01-13 15:08 ` John P. Linderman
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=20220113020314.GN61872@eureka.lemis.com \
--to=grog@lemis.com \
--cc=coff@tuhs.org \
--cc=joshnatis0@gmail.com \
/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).