ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: news3@nililand.de, mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Using the standalone ConTeXt, how do I add access to my texmf-local tree
Date: Thu, 05 Mar 2015 01:40:06 +0100	[thread overview]
Message-ID: <54F7A5E6.9070105@wxs.nl> (raw)
In-Reply-To: <12qzzohepaf5n$.dlg@nililand.de>

On 3/4/2015 7:06 PM, Ulrike Fischer wrote:
> Am Wed, 04 Mar 2015 17:58:24 +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

> 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

(in general it's best to use a context garden tree with garden binaries 
as there we use beta bins)

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2015-03-05  0:40 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 [this message]
2015-03-05  9:34                       ` Ulrike Fischer
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=54F7A5E6.9070105@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=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).