From: sl@stanleylieber.com
To: 9front@9front.org
Subject: Re: 9front@9front.org FAILED
Date: Tue, 13 Feb 2018 19:39:52 -0500 [thread overview]
Message-ID: <4EC1E1C6D7C270EEEF131B1959425B9E@5ess.inri.net> (raw)
In-Reply-To: FA29E0C15F6DE7BB820BB920960CE5D9@9front.org
For uknown reasons, iOS mail client insisted on replying to this message
in HTML, which was rejected by the list. Here is my message again:
On Feb 13, 2018, at 11:19 AM, Lyndon Nerenberg <lyndon@orthanc.ca> wrote:
>> 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?
>=20
> The reference string 'tex(1)' expliticly says there is a section one manpa=
ge of that name, and that's wrong.
>=20
> I would replace it with a reference to the TUG web site (https://tug.org)
Based on the man pages, it looks like 2ed shipped with it:
http://man.cat-v.org/plan_9_2nd_ed/1/tex
sl
next reply other threads:[~2018-02-14 0:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 0:39 sl [this message]
2018-10-11 13:34 Stanley Lieber
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=4EC1E1C6D7C270EEEF131B1959425B9E@5ess.inri.net \
--to=sl@stanleylieber.com \
--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).