From: Jaap Akkerhuis <jaapna@xs4all.nl>
To: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Documenter's Workbench versions
Date: Wed, 9 Mar 2022 10:41:54 +0100 [thread overview]
Message-ID: <C1B54916-71B4-4AF0-BF0E-03BFF376E4B2@xs4all.nl> (raw)
In-Reply-To: <CAKH6PiXBXNt12sKaJ7ud7FQCsgxJxYyAKwv2HhRzErT2Jc-6mg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 418 bytes --]
> On Mar 9, 2022, at 3:06, Douglas McIlroy <douglas.mcilroy@dartmouth.edu> wrote:
>
> <SNIP>
> Document preparation became a widespread use
> of Unix, but no stand-alone word-processing system was ever undertaken.
I do seem to remember an attempt by some outfit to sell a standalone
word processors based on troff, but U don't remember the name. It
wasn't a success and failed very quickly.
jaap
[-- Attachment #1.2: Type: text/html, Size: 2939 bytes --]
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 267 bytes --]
next prev parent reply other threads:[~2022-03-09 9:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 2:06 Douglas McIlroy
2022-03-09 9:41 ` Jaap Akkerhuis [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-07 1:02 Kevin Bowling
2022-03-07 2:42 ` Larry McVoy
2022-03-07 13:28 ` Jaap Akkerhuis
2022-03-07 16:55 ` Kevin Bowling
2022-03-10 17:21 ` ozan yigit
2022-03-07 20:57 ` Kevin Bowling
2022-03-09 22:30 ` Andrew Diller
2022-03-10 0:44 ` Kevin Bowling
2022-03-10 2:17 ` Andrew Diller
2022-03-10 1:10 ` Dan Plassche
2022-03-14 0:17 ` Dan Plassche
2022-03-13 5:24 ` Warren Toomey
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=C1B54916-71B4-4AF0-BF0E-03BFF376E4B2@xs4all.nl \
--to=jaapna@xs4all.nl \
--cc=douglas.mcilroy@dartmouth.edu \
--cc=tuhs@minnie.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).