ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
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: Wed, 4 Mar 2015 14:52:24 +0100	[thread overview]
Message-ID: <uz4g70pohcv2.dlg@nililand.de> (raw)
In-Reply-To: <54F42129.5010801@wxs.nl>

Am Mon, 02 Mar 2015 09:36:57 +0100 schrieb Hans Hagen:

>> Can I adapt that in some way, so I can add a few texmfs to the search
>> path? I have no problem with adapting a file or setting an environment
>> variable.
> 
> texmfcnf.lua (can be in your texmf-local tree) or the TEXMF env var; not 
> so different from regular texlive, only in a different configuration file

I have a question regarding texmcnf.lua + TEXMCNF:

On my system TEXMFCNF points to a folder where I have a special
texmf.cnf that I need for texlive. 

This disturbs context:

resolvers       | resolving | looking for 'texmfcnf.lua' on weird
path 'D:/texmfcnf/' from specification 'D:/texmfcnf/'

and as there is not texmfcnf.lua the search pathes can't be setup.

I would like to add a texmfcnf.lua there which helps context to find
and load the standard configuration. What should be the content of
such a texmfcnf.lua?

I tried with

return {
    type    = "configuration",
    version = "1.",
    date    = "2015-03-04",
    time    = "14:00:00",
    comment = "ConTeXt MkIV configuration file",
    author  = "Ulrike Fischer",
    content = {
       variables = {
       TEXMFCNF     =
{"D:/context-minimals/context/tex/texmf/web2c"}
                   }
               }
        }


but it didn't work ;-(. This doesn't setup the pathes.

I also tried
dofile("D:/context-minimals/context/tex/texmf/web2c/texmfcnf.lua")

which didn't work either. 

-- 
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
___________________________________________________________________________________

  reply	other threads:[~2015-03-04 13:52 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 [this message]
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
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=uz4g70pohcv2.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).