From: Nikolai Weibull <context-list@pcppopper.org>
Subject: Re: Getting linuxtex.zip working
Date: Mon, 1 Nov 2004 15:22:11 +0100 [thread overview]
Message-ID: <20041101142211.GC9161@puritan.pcp.ath.cx> (raw)
In-Reply-To: <418603B3.9010801@wxs.nl>
* Hans Hagen <pragma@wxs.nl> [Nov 01, 2004 13:55]:
> > 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
Sure, but what variables are actually necessary to export and, more
interestingly, why are they needed in the environment at all? When
running from tetex everything works fine. I'm guessing this is mostly
due to differences between stuff in tetex 2.0.2 and more recent releases
of software, but I still can't see why it would be necessary to fill the
environment with some 10-20 variables.
nikolai (the environmentalist)
--
::: name: Nikolai Weibull :: aliases: pcp / lone-star / aka :::
::: born: Chicago, IL USA :: loc atm: Gothenburg, Sweden :::
::: page: www.pcppopper.org :: fun atm: gf,lps,ruby,lisp,war3 :::
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}
next prev parent reply other threads:[~2004-11-01 14:22 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
2004-11-01 14:22 ` Nikolai Weibull [this message]
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=20041101142211.GC9161@puritan.pcp.ath.cx \
--to=context-list@pcppopper.org \
--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).