From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: 9front@9front.org
Subject: Re: [9front] Extraneous tex(1) References
Date: Tue, 13 Feb 2018 08:19:56 -0800 (PST) [thread overview]
Message-ID: <alpine.BSF.2.21.1802130817510.58338@orthanc.ca> (raw)
In-Reply-To: <E5239AA97CE2FB9E9206FBD43D6530D5@5ess.inri.net>
> While 9front (and Plan 9 from Bell Labs, for that matter) does not
> ship with tex, the utilities listed above do perform operations on tex
> files. What should be the proper way to change these references?
The reference string 'tex(1)' expliticly says there is a section one
manpage of that name, and that's wrong.
I would replace it with a reference to the TUG web site (https://tug.org).
next prev parent reply other threads:[~2018-02-13 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 23:43 sl
2018-02-13 16:19 ` Lyndon Nerenberg [this message]
2018-02-12 23:45 cinap_lenrek
2018-02-13 17:54 ` Sean Hinchee
2018-02-13 22:03 ` jamos
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=alpine.BSF.2.21.1802130817510.58338@orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=9front@9front.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).