From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Getting linuxtex.zip working
Date: Mon, 01 Nov 2004 10:36:51 +0100 [thread overview]
Message-ID: <418603B3.9010801@wxs.nl> (raw)
In-Reply-To: <20041031223402.GB9821@puritan.pcp.ath.cx>
Nikolai Weibull wrote:
> Exactly what do I need to do after running setuptex, mktexlsr, and
> texexec --make --alone? PATH needs permanent updating for sure, but
> what else? texexec won't work (kpsewhich won't work) unless setuptex is
> sourced before I try running it in a fresh shell. What am I missing in
> my setup?
you can add the call to setuptex to your local profile
. /path-to/setuptex /path-to
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2004-11-01 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-31 22:34 Nikolai Weibull
2004-11-01 9:36 ` Hans Hagen [this message]
2004-11-01 14:22 ` Nikolai Weibull
2004-11-01 14:39 ` Hans Hagen
2004-11-02 7:40 ` Henning Hraban Ramm
2004-11-02 10:14 ` Uwe Koloska
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=418603B3.9010801@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/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).