From: Larry McVoy <lm@mcvoy.com>
To: Jon Steinhart <jon@fourwinds.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Demise of TeX and groff (was: roff(7))
Date: Tue, 11 Jan 2022 12:36:18 -0800 [thread overview]
Message-ID: <20220111203618.GA3441@mcvoy.com> (raw)
In-Reply-To: <202201112026.20BKQC9r2356242@darkstar.fourwinds.com>
On Tue, Jan 11, 2022 at 12:26:12PM -0800, Jon Steinhart wrote:
> Larry McVoy writes:
> > On Tue, Jan 11, 2022 at 12:15:43PM -0800, Jon Steinhart wrote:
> > > The big thing missing from *roff from a publishing point of view is
> > > a good way to make comments and respond to them. Kind of a must-have
> > > when working with human (not text) editors.
> >
> > Source code control for the win.
>
> Well, you're correct, but not practical with human editors. I'm not
> talking about revision history, I'm talking about the ability to easily
> highlight a portion of text and comment "did you mean foo?" and so on.
> That part of the production process feedback loop is missing. Of course,
> with *roff one could mostly produce one's own stuff without needing human
> editors and a production staff.
I wrote the GUIs for BitKeeper, I could absolutely give you exactly
what you want. Really, what you are describing is our code review
system which could done done completely in a web browser but if you
needed to hack on things, you cloned it and hacked on it and pushed.
--
---
Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm
next prev parent reply other threads:[~2022-01-11 20:36 UTC|newest]
Thread overview: 102+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 15:47 [TUHS] roff(7) Douglas McIlroy
2021-12-31 23:07 ` George Michaelson
2021-12-31 23:40 ` Larry McVoy
2022-01-01 0:56 ` [TUHS] TeX and groff (was: roff(7)) Greg 'groggy' Lehey
2022-01-01 3:15 ` Larry McVoy
2022-01-10 19:00 ` Blake McBride
2022-01-10 20:21 ` Jon Forrest
2022-01-11 22:48 ` Blake McBride
2022-01-11 23:18 ` Larry McVoy
2022-01-12 1:19 ` Dave Horsfall
2022-01-12 1:46 ` Blake McBride
2022-01-12 2:12 ` Bakul Shah
2022-01-12 15:49 ` Larry McVoy
2022-01-12 16:22 ` Adam Thornton
2022-01-12 0:06 ` Jon Steinhart
2022-01-12 1:48 ` Blake McBride
2022-01-12 0:29 ` Nemo Nusquam
2022-01-12 1:53 ` Blake McBride
[not found] ` <E3CC4B8A-4E88-4339-A4D3-4ED26BA80620@gmail.com>
2022-01-12 0:44 ` Jon Forrest
2022-01-12 2:00 ` Blake McBride
2022-01-12 2:10 ` David Arnold
2022-01-12 2:26 ` Adam Thornton
2022-01-12 19:54 ` John Cowan
2022-01-13 10:13 ` Thomas Paulsen
2022-01-13 20:00 ` John Cowan
2022-01-10 20:33 ` Larry McVoy
2022-01-10 20:37 ` Richard Salz
2022-01-10 21:04 ` Dan Cross
2022-01-10 21:48 ` Nemo Nusquam
2022-01-11 2:25 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-01-11 2:47 ` Larry McVoy
2022-01-22 2:34 ` [TUHS] troff environments, traps, and diversions (was: TeX and groff) Branden Robinson
2022-01-22 16:02 ` Douglas McIlroy
2022-01-23 19:45 ` Jon Steinhart
2022-01-23 22:26 ` Jon Steinhart
2022-01-11 1:52 ` [TUHS] Recognizing TeX (was: TeX and groff (was: roff(7))) Greg 'groggy' Lehey
2022-01-12 1:19 ` [TUHS] TeX and groff (was: roff(7)) Mary Ann Horton
2022-01-12 2:03 ` Blake McBride
2022-01-12 2:10 ` Bakul Shah
2022-01-12 3:44 ` Dan Cross
2022-01-12 16:48 ` Steffen Nurpmeso
2022-01-10 20:46 ` Steffen Nurpmeso
2022-01-11 1:59 ` [TUHS] Demise of " Greg 'groggy' Lehey
2022-01-11 2:13 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-01-11 2:42 ` Larry McVoy
2022-01-11 5:12 ` Greg 'groggy' Lehey
2022-01-11 5:59 ` John Labovitz
2022-01-11 8:57 ` arnold
2022-01-11 20:15 ` Jon Steinhart
2022-01-11 20:22 ` Larry McVoy
2022-01-11 20:26 ` Jon Steinhart
2022-01-11 20:36 ` Larry McVoy [this message]
2022-01-11 20:41 ` Jon Steinhart
2022-01-11 20:49 ` Larry McVoy
2022-01-11 21:03 ` Jon Steinhart
2022-01-11 8:50 ` arnold
2022-01-11 14:00 ` Larry McVoy
2022-01-12 23:22 ` [TUHS] troff or groff? (was: Demise of TeX and groff (was: roff(7))) Greg 'groggy' Lehey
2022-01-12 23:29 ` Greg 'groggy' Lehey
2022-01-12 23:32 ` Larry McVoy
2022-01-11 15:47 ` [TUHS] Demise of TeX and groff (was: roff(7)) Clem Cole
2022-01-11 16:55 ` Richard Salz
2022-01-11 18:49 ` Clem Cole
2022-01-11 19:20 ` John Cowan
2022-01-11 20:06 ` Clem Cole
2022-01-11 23:57 ` Warner Losh
2022-01-12 0:03 ` Warner Losh
2022-01-12 8:54 ` arnold
2022-01-12 15:17 ` Clem Cole
2022-01-12 16:33 ` Dan Cross
2022-01-12 18:06 ` [TUHS] *roff history as told to GNU G. Branden Robinson
2022-01-12 18:34 ` Dan Halbert
2022-01-12 22:48 ` Clem Cole
2022-01-12 23:27 ` Charles H. Sauer
2022-01-13 0:35 ` Adam Thornton
2022-01-12 20:01 ` Dan Cross
2022-01-12 22:32 ` Clem Cole
2022-01-13 2:38 ` John Labovitz
2022-01-13 7:42 ` Lars Brinkhoff
2022-01-13 13:47 ` John Labovitz
2022-01-12 8:48 ` [TUHS] Demise of TeX and groff (was: roff(7)) arnold
2022-01-12 15:51 ` Larry McVoy
2022-01-12 15:57 ` Clem Cole
2022-01-12 15:56 ` Clem Cole
2022-01-11 3:22 ` Adam Thornton
2022-01-12 0:32 ` Nemo Nusquam
2022-01-01 20:00 ` [TUHS] roff(7) [ and other related stuff ] Jon Steinhart
2022-01-02 0:12 ` Larry McVoy
2022-01-02 1:04 ` John Cowan
2022-01-02 1:20 ` Larry McVoy
2022-01-02 1:47 ` Steve Nickolas
2022-01-02 2:12 ` Larry McVoy
2022-01-02 3:56 ` Jon Steinhart
2022-01-02 1:48 ` Jon Steinhart
2022-01-02 3:04 ` John Cowan
2022-01-02 3:30 ` Warner Losh
2022-01-01 1:11 ` [TUHS] roff(7) Phil Budne
2022-01-01 1:17 ` Chris Torek
2022-01-01 3:06 ` Larry McVoy
2022-01-01 3:34 ` George Michaelson
2022-01-05 21:15 ` Tony Finch
2022-01-11 22:02 [TUHS] Demise of TeX and groff (was: roff(7)) Douglas McIlroy
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=20220111203618.GA3441@mcvoy.com \
--to=lm@mcvoy.com \
--cc=jon@fourwinds.com \
--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).