From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] RIP J.F.Ossanna
Date: Wed, 29 Nov 2017 18:48:16 -0800 [thread overview]
Message-ID: <20171130024816.GI16794@mcvoy.com> (raw)
In-Reply-To: <20171129190055.9ZFVf%steffen@sdaoden.eu>
On Wed, Nov 29, 2017 at 08:00:55PM +0100, Steffen Nurpmeso wrote:
> Larry McVoy <lm at mcvoy.com> wrote:
> |On Mon, Nov 27, 2017 at 07:06:51PM -0500, Ron Natalie wrote:
> |> 1977 marks my entry into the world of UNIX. I've always stated there was
> |> only one person who truly understood nroff and he was dead.
> |> I mourn the fact that of all the UNIX greats I've met, I missed out on
> |> Ossanna.
>
> |I think one could argue that James Clark has a pretty good handle on
> |roff (having written the GNU version of nroff/troff/tbl/eqn/pic etc).
>
> And Werner Lemberg, who carried the torch for the last almost two
> decades. He brought in some really great improvements, like
> arguments for strings, which allows to write pretty much TeX like
> a.k.a. inline if you want to (as in "this is \*[I talic] text").
Yep. James exited stage left and Werner stepped in. I mean no disrespect
to anyone, I was just saying that James has a really good handle on roff,
he redid it all. I admire him for doing so (even though I curse the fact
that he did it in C++).
next prev parent reply other threads:[~2017-11-30 2:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 22:05 Dave Horsfall
2017-11-28 0:06 ` Ron Natalie
2017-11-28 0:15 ` Larry McVoy
[not found] ` <20171129190055.9ZFVf%steffen@sdaoden.eu>
2017-11-30 2:48 ` Larry McVoy [this message]
2017-11-30 15:44 ` Steffen Nurpmeso
2017-11-30 20:43 ` Noel Hunt
2017-11-30 22:36 ` Steffen Nurpmeso
2017-11-28 0:14 ` Larry McVoy
-- strict thread matches above, loose matches on Subject: below --
2016-11-28 0:11 Norman Wilson
2016-11-27 22:15 Dave Horsfall
2016-11-27 22:17 ` Ron Natalie
2016-11-27 22:28 ` Larry McVoy
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=20171130024816.GI16794@mcvoy.com \
--to=lm@mcvoy.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).