From: Yanrui Li <liyanrui.m2@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: setuptex changes in minimals (was: bugs in beta)
Date: Fri, 8 May 2009 20:16:21 +0800 [thread overview]
Message-ID: <c3f901470905080516q37b4ac89n30ff1e08540c7c98@mail.gmail.com> (raw)
In-Reply-To: <6faad9f00905080419m4c8064biaefd5189bae5aa13@mail.gmail.com>
On Fri, May 8, 2009 at 7:19 PM, Mojca Miklavec
<mojca.miklavec.lists@gmail.com> wrote:
> On Fri, May 8, 2009 at 11:46, Yanrui Li wrote:
>>
>> Recently I have found some environment variables in setuptex script
>> are commented out sometimes, such as TEXMFLOCAL, TEXMFCONTEXT and so
>> on. Is this be done deliberately?
>
> Yes (we were bored during some Polish talks at BachoTeX).
>
> The reason for setuptex setting all those variables in the old days
> was to override tetex's environmental variables, but in principle this
> is not needed at all unless tetex is present on computer. The reason
> for removing them again was to make sure that Hans' scripts work
> properly even when no environmental variable is set (which will be the
> case on TeX Live for example).
>
> The only variable change that's really needed is fixing PATH, but it's
> so convenient to be able to run
> ". /path/to/setuptex"
> instead of typing the long
> export PATH="/path/to/minimals/bin:$PATH"
>
> We nevertheless left two or three variables since ConTeXt didn't yet
> work properly without them, but we'll remove those as well.
>
> If anyone uses minimals on tetex, we can create an additional file
> again that would enable complete isolation.
>
> We didn't clean up the windows script yet as it would need some more
> testing (and we had enough problem by minimals not running at all on
> unix), but that's still on TODO list ...
>
> We also silently added TEXMFHOME (while Hans was not watching), but
> maybe we need to change the exact path.
>
> If you have any particular question or request about that, let us know.
>
Thanks for your explanation. Now I see.
I have no questions for these, only I have to modify instruction of these
variables in the tutorial which I wrote for Chinese users :)
--
Best wishes,
Li Yanrui
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-05-08 12:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 11:19 Mojca Miklavec
2009-05-08 12:16 ` Yanrui Li [this message]
2009-05-08 17:43 ` Mojca Miklavec
2009-05-08 18:17 ` Yanrui Li
2009-05-08 18:20 ` Yanrui Li
2009-05-09 1:57 ` Yue Wang
2009-05-09 8:02 ` setuptex changes in minimals Hans Hagen
2009-05-09 11:44 ` Yanrui Li
2009-05-09 15:57 ` Yue Wang
2009-05-10 15:35 ` Hans Hagen
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=c3f901470905080516q37b4ac89n30ff1e08540c7c98@mail.gmail.com \
--to=liyanrui.m2@gmail.com \
--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).