The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "John P. Linderman" <jpl.jpl@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.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 10:49:52 -0500	[thread overview]
Message-ID: <CAC0cEp-urPFt93eNNtFFoS3=yVCc4Ts8ijgvZ4uDzs4R9R7M4Q@mail.gmail.com> (raw)
In-Reply-To: <20210222033217.dkqavclp22sa77ln@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 625 bytes --]

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: 733 bytes --]

  parent reply	other threads:[~2021-02-22 15:50 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 [this message]
2021-02-22 15:57     ` William Cheswick
2021-02-22 16:03       ` John P. Linderman
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-urPFt93eNNtFFoS3=yVCc4Ts8ijgvZ4uDzs4R9R7M4Q@mail.gmail.com' \
    --to=jpl.jpl@gmail.com \
    --cc=g.branden.robinson@gmail.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).