From: "John P. Linderman" <jpl.jpl@gmail.com>
To: William Cheswick <ches@cheswick.com>
Cc: The Unix Heritage Society <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Proliferation of options is great simplification of pipes, really?
Date: Mon, 22 Feb 2021 11:03:43 -0500 [thread overview]
Message-ID: <CAC0cEp-72A3vQn_1oF-TsLGNf5LXqaopPyzgb2KiVOqi7Bs+NQ@mail.gmail.com> (raw)
In-Reply-To: <E4DEAC7C-E745-44D6-8CC9-B406C627D168@cheswick.com>
[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]
On a brute-forcier note, when I was doing a lot more troff, I wrote a
command that ran input through *ALL* the preprocessors I might need. Even
on 70's processors, it was fast enough, and msde my life a tiny bit
better. -- jpl
On Mon, Feb 22, 2021 at 10:57 AM William Cheswick <ches@cheswick.com> wrote:
> This proposal reminds me of Paul Glick’s lp command. It took whatever
> file you gave it, and processed
> it as necessary for whatever printer you chose. It was very useful,
> simple AI.
>
> > On Feb 22, 2021, at 10:49 AM, John P. Linderman <jpl.jpl@gmail.com>
> wrote:
> >
> > I can imagine a simple perl (or python or whatever) script that would
> run through groff input, determine which preprocessors are actually needed,
> and set up a pipeline to run through (only) the needed preprocessors in the
> proper order. I wouldn't have to tell groff what preprocessors I think are
> needed, and groff wouldn't have to change (although my script would) when
> another preprocessor comes into existence. Modern processors are fast
> enough, and groff input small enough, that the "extra" pass wouldn't be
> burdensome. And it would take the burden off me to remember exactly which
> preprocessors are essential. -- jpl
>
>
[-- Attachment #2: Type: text/html, Size: 1672 bytes --]
next prev parent reply other threads:[~2021-02-22 16:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 2:34 Will Senn
2021-02-22 3:32 ` G. Branden Robinson
2021-02-22 4:32 ` Dan Stromberg
2021-02-22 4:34 ` Will Senn
2021-02-22 5:45 ` G. Branden Robinson
2021-02-22 15:49 ` John P. Linderman
2021-02-22 15:57 ` William Cheswick
2021-02-22 16:03 ` John P. Linderman [this message]
2021-02-22 21:16 ` G. Branden Robinson
2021-02-22 16:02 ` Warner Losh
2021-02-22 16:12 ` Robert Clausecker
2021-02-22 17:15 ` John Cowan
2021-02-23 0:24 ` Steffen Nurpmeso
2021-02-22 21:14 ` G. Branden Robinson
2021-02-22 7:20 ` Rich Morin
2021-02-22 18:27 ` Jon Steinhart
2021-02-22 19:30 ` Richard Salz
2021-02-23 2:47 M Douglas McIlroy
2021-02-23 10:42 ` Jaap Akkerhuis
2021-02-23 13:23 ` Brantley Coile
2021-02-23 13:49 ` Ralph Corderoy
2021-02-23 15:04 Steve Simon
2021-02-24 2:42 ` M Douglas McIlroy
2021-02-24 19:38 Norman Wilson
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-72A3vQn_1oF-TsLGNf5LXqaopPyzgb2KiVOqi7Bs+NQ@mail.gmail.com \
--to=jpl.jpl@gmail.com \
--cc=ches@cheswick.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).