From: Ralph Corderoy <ralph@inputplus.co.uk>
To: M Douglas McIlroy <m.douglas.mcilroy@dartmouth.edu>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Proliferation of options is great simplification of pipes, really?
Date: Tue, 23 Feb 2021 13:49:59 +0000 [thread overview]
Message-ID: <20210223134959.0EEC2219D9@orac.inputplus.co.uk> (raw)
In-Reply-To: <CAKH6PiV6xK0-F9XJc3RtzJpcURUUMZgpK6VVZD5uoFqOKaLGyQ@mail.gmail.com>
Hi Doug,
> > I can imagine a simple perl (or python or whatever) script that
> > would run through groff input [and] determine which preprocessors
> > are actually needed ...
>
> Brian imagined such and implemented it way back when. Though I used
> it, I've forgotten its name.
Was it ‘doctype’? That's what it's called in Kernighan & Pike's ‘Unix
Programming Environment’, pp. 306-8. Groff had something similar called
grog(1) which had flaws when I rewrote it in sh and mainly awk back
in 2002. (My version never made it in because an FSF copyright
assignment was required and their answers to some of my questions meant
I wouldn't sign.) Someone else since rewrote Groff's in Perl.
> defensive groff -pet that I often use
I've taken to putting the information needed as a comment at the start
of the main source file whence it's picked up by a generic run-off
script. Similar to man(1) looking for a «'\"» comment with code
letters: ‘p’ for pic, ‘v’ for vgrind, etc.
--
Cheers, Ralph.
next prev parent reply other threads:[~2021-02-23 13:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-02-24 19:38 Norman Wilson
2021-02-23 15:04 Steve Simon
2021-02-24 2:42 ` M Douglas McIlroy
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
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
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=20210223134959.0EEC2219D9@orac.inputplus.co.uk \
--to=ralph@inputplus.co.uk \
--cc=m.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).