From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: Re: Using the standalone ConTeXt, how do I add access to my texmf-local tree
Date: Thu, 5 Mar 2015 10:34:04 +0100 [thread overview]
Message-ID: <18haccocyynlc.dlg@nililand.de> (raw)
In-Reply-To: <54F7A5E6.9070105@wxs.nl>
Am Thu, 05 Mar 2015 01:40:06 +0100 schrieb Hans Hagen:
>>> You can try in texmf-local/web2c:
>> ...
>>
>> This doesn't help: context never looks in texmf-local/web2c. It
>> looks into D:/texmfcnf and then stops.
>
> hm, normally it will look relative to the binary, in trees/web2c paths
Yes, but as I have set the environment variable TEXMFCNF I have
overwritten the normal behaviour.
>> But I just realized that I have actually two context (one in
>> texlive 2014) and trying to setup the systems with a texmfcnf.lua
>> will probably give a complete mess. So I will revert to my normal
>> system where I change the environment variables first.
>
> ok; taking bins from one tex tree (full tree) and expecting them to work
> with another one is tricky due all this auto-magic; in that case setting
> the TEXMF variable as environment variable might help
Sorry this is a misunderstanding: I'm not trying to mix two context
versions. I want to use the standalone binaries with the standalone
trees, and perhaps the texlive context binaries with the texlive
tree. Beside this I also want to use miktex, texlive 2014, and
sometimes (for debugging) texlive 2013 ;-);
Sorting out all this installations so that they don't interfer isn't
easy.
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2015-03-05 9:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 10:48 Gerben Wierda
2015-03-01 10:59 ` Hans Hagen
2015-03-01 21:56 ` Gerben Wierda
2015-03-01 22:04 ` Wolfgang Schuster
2015-03-01 22:16 ` Gerben Wierda
2015-03-01 23:15 ` Wolfgang Schuster
2015-03-02 6:42 ` Gerben Wierda
2015-03-02 8:36 ` Hans Hagen
2015-03-04 13:52 ` Ulrike Fischer
2015-03-04 16:58 ` Hans Hagen
2015-03-04 18:06 ` Ulrike Fischer
2015-03-05 0:40 ` Hans Hagen
2015-03-05 9:34 ` Ulrike Fischer [this message]
2015-03-06 8:22 ` Procházka Lukáš Ing. - Pontex s. r. o.
2015-03-06 9:52 ` Hans Hagen
2015-03-06 9:59 ` Hans Hagen
2015-03-06 12:08 ` Procházka Lukáš Ing. - Pontex s. r. o.
2015-03-06 13:45 ` Hans Hagen
2015-03-06 14:14 ` Procházka Lukáš Ing. - Pontex s. r. o.
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=18haccocyynlc.dlg@nililand.de \
--to=news3@nililand.de \
--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).