9front - general discussion about 9front
 help / color / mirror / Atom feed
From: jamos@oboj.net
To: 9front@9front.org
Subject: Re: [9front] Extraneous tex(1) References
Date: Wed, 14 Feb 2018 00:03:03 +0200	[thread overview]
Message-ID: <16ec38a6ede5f95b79a1f08493904d17@oboj.net> (raw)
In-Reply-To: <bbf165c3-4b3e-380c-0900-313adecf448e@gmail.com>

Maybe kerTeX by Thierry Laronde?

Jonas A

On 2018-02-13 19:54, Sean Hinchee wrote:
> Is there a tex(1) to install?
> 
> If desired I can write patches to reword the sentences around the
> tex(1) references to imply tex file application.
> 
> sean
> 
> On 02/12/2018 05:45 PM, cinap_lenrek@felloff.net wrote:
>> ignore it or install tex.
>> 
>> --
>> cinap
>> 


  reply	other threads:[~2018-02-13 22:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12 23:45 cinap_lenrek
2018-02-13 17:54 ` Sean Hinchee
2018-02-13 22:03   ` jamos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-02-12 23:43 sl
2018-02-13 16:19 ` Lyndon Nerenberg

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=16ec38a6ede5f95b79a1f08493904d17@oboj.net \
    --to=jamos@oboj.net \
    --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).