The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: saint.snit@gmail.com
To: tuhs@minnie.tuhs.org
Subject: [TUHS] revision history of troff -me macro set?
Date: Mon, 14 Sep 2020 14:33:04 -0500	[thread overview]
Message-ID: <5f5fc849.1c69fb81.8127c.ee16@mx.google.com> (raw)

Hi,

Is there a repository of historical versions of Eric Allman's -me macro
set for troff?

(For some context: the macro set has been forked to operate with two
modern troff implementations: GNU groff and Heirloom troff.  According
to the header blocks of the respective files, groff's -me macros are
forked from version 2.31 of Allman's, and Heirloom's from version 2.14.
For help in debugging -me problems in these troff implementations,
I'm trying to locate at least these versions of the -me package as they
existed before forking.  I posted this query on the troff email list,
but no one there knew the answer, and one person suggested I ask here.)

Thanks for any pointers.

             reply	other threads:[~2020-09-14 19:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14 19:33 saint.snit [this message]
2020-09-14 20:02 ` Warner Losh
2020-09-14 20:08   ` Henry Bent
2020-09-14 20:57 ` Eric Allman
2020-09-14 21:41 ` Jeremy C. Reed
2020-09-17  6:20 saint.snit

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=5f5fc849.1c69fb81.8127c.ee16@mx.google.com \
    --to=saint.snit@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).