* Re: [9front] Extraneous tex(1) References
@ 2018-02-12 23:45 cinap_lenrek
2018-02-13 17:54 ` Sean Hinchee
0 siblings, 1 reply; 5+ messages in thread
From: cinap_lenrek @ 2018-02-12 23:45 UTC (permalink / raw)
To: 9front
ignore it or install tex.
--
cinap
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [9front] Extraneous tex(1) References
@ 2018-02-12 23:43 sl
2018-02-13 16:19 ` Lyndon Nerenberg
0 siblings, 1 reply; 5+ messages in thread
From: sl @ 2018-02-12 23:43 UTC (permalink / raw)
To: 9front
> There's a handful of manuals that reference a non-existent tex(1) manual page:
>
> * deroff(1)
> * lp(1)
> * page(1)
> * pic(1)
> * troff(1)
> * lp(8)
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?
sl
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [9front] Extraneous tex(1) References
2018-02-12 23:43 sl
@ 2018-02-13 16:19 ` Lyndon Nerenberg
0 siblings, 0 replies; 5+ messages in thread
From: Lyndon Nerenberg @ 2018-02-13 16:19 UTC (permalink / raw)
To: 9front
> 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).
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2018-02-13 22:03 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-02-12 23:45 [9front] Extraneous tex(1) References cinap_lenrek
2018-02-13 17:54 ` Sean Hinchee
2018-02-13 22:03 ` jamos
-- strict thread matches above, loose matches on Subject: below --
2018-02-12 23:43 sl
2018-02-13 16:19 ` Lyndon Nerenberg
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).