From: Sean Hinchee <henesy.dev@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Re: TeX
Date: Sun, 18 Feb 2018 13:56:13 -0600 [thread overview]
Message-ID: <7ed889ff-4016-23f3-e952-5d61e3c0597b@gmail.com> (raw)
In-Reply-To: <3BA50356-B2F3-49A7-8E72-E332C5D619EF@quintile.net>
I started this mess and I'm sorry for that. Although it's not perfect, I
took the package kurt linked (tex.iso.bz2) and have adjusted the build a
bit and it is now stuffed in ports. Like steve said, there is also kertex.
Cheers,
Sean
On 02/18/2018 06:04 AM, Steve Simon wrote:
> but someone did, kertex!
>
>
>> On 18 Feb 2018, at 06:55, Matthew Veety <mveety@gmail.com> wrote:
>>
>>> On Wednesday, February 14, 2018 09:15:25 Steve Simon wrote:
>>> why mot have tex(1) manpage which states that rex is not included by default
>>> but gives a weblink for a recommended tex package, e.g. kertex, which is
>>> tested on an9.
>>>
>>> this manpage would then be overwritten by the tex installation.
>>>
>>> everyone happy (unlikely)
>>>
>>> -Steve
>>
>> If someone makes a port for some TeX package that does this I would be okay
>> with it. Knowing that certainly won't happen unless I do it, the references
>> really just should be nuked. If a package doesn't ship with 9front it
>> shouldn't be in they system's manpages.
>>
>> --
>> Veety
>
next prev parent reply other threads:[~2018-02-18 19:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 1:59 TeX Lyndon Nerenberg
2018-02-14 9:15 ` [9front] TeX Steve Simon
2018-02-18 6:55 ` Matthew Veety
2018-02-18 12:04 ` Steve Simon
2018-02-18 19:56 ` Sean Hinchee [this message]
2018-02-19 4:32 ` Matthew Veety
2018-02-18 14:12 ` hiro
2018-02-18 17:18 ` Steve Simon
2018-02-14 2:23 sl
2018-02-19 23:26 sl
2018-02-20 9:04 ` Julius Schmidt
2018-02-20 13:22 ` Ethan Grammatikidis
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=7ed889ff-4016-23f3-e952-5d61e3c0597b@gmail.com \
--to=henesy.dev@gmail.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).