From: Andrew Hume <andrew@humeweb.com>
To: segaloco <segaloco@protonmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Trying to date "A Supplemental Document For Awk"
Date: Wed, 28 Jun 2023 23:41:53 -0700 [thread overview]
Message-ID: <FBC900FB-1F74-492D-A673-E915133D49D9@humeweb.com> (raw)
In-Reply-To: <PvNODLfIjHFhDm9v5quj86w8VG5VgBts6bbtOZHCCBJZ2YtA2JDTVo3HeDDrqMsJqSx0a742ByOSiZOFAgAJLGO0TqJRp_Kef_axQAa7teQ=@protonmail.com>
over time, folks in research tended to use make (or its descendants) to generate paper outputs.
altho i do recall a tool similar to grog that correctly orchestrated the ideal/pic/eqn/tbl/troff pipeline
needed to generate the output. the order was important.
as for macros, for several years we tended to use the pm macros (akin to the ms macros)
because they drove chris van wyck and kernighan’s page balancing backend, which was necessary
to produce print ready copy for journals etc.
> On Jun 28, 2023, at 11:27 PM, segaloco via TUHS <tuhs@tuhs.org> wrote:
>
>> But what did people use before grog and why was the compilation line
>> never placed in a comment in the file?
next prev parent reply other threads:[~2023-06-29 6:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 6:26 [TUHS] " Aharon Robbins
2023-06-28 6:45 ` [TUHS] " arnold
2023-06-28 17:48 ` Adam Sampson
2023-06-28 18:03 ` KenUnix
2023-06-28 18:38 ` Clem Cole
2023-06-28 23:47 ` Greg 'groggy' Lehey
2023-06-29 1:59 ` Stuff Received
2023-06-29 6:27 ` segaloco via TUHS
2023-06-29 6:41 ` Andrew Hume [this message]
2023-06-29 6:45 ` Noel Hunt
2023-06-29 6:48 ` Andrew Hume
2023-06-29 6:50 ` arnold
2023-06-29 6:44 ` Noel Hunt
2023-06-29 14:02 ` G. Branden Robinson
2023-06-29 13:45 ` G. Branden Robinson
2023-06-29 13:34 ` G. Branden Robinson
2023-06-29 13:47 ` Rich Salz
2023-06-29 19:03 ` Steffen Nurpmeso
2023-06-29 1:04 ` Bakul Shah
2023-06-29 0:26 ` Jeremy C. Reed
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=FBC900FB-1F74-492D-A673-E915133D49D9@humeweb.com \
--to=andrew@humeweb.com \
--cc=segaloco@protonmail.com \
--cc=tuhs@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).