ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: trouble starting context
Date: Thu, 03 Jul 2008 11:18:54 +0200	[thread overview]
Message-ID: <486C997E.4090503@elvenkind.com> (raw)
In-Reply-To: <m2vdznaiba.fsf@stanford.edu>



Jesse Alama wrote:
> Taco Hoekwater <taco@elvenkind.com> writes:
>>
>> I have:
>>
>> LUAINPUTS=.;$TEXMF/tex/{context,plain/base,generic}//:$TEXMF/scripts/context/lua
>> TEXMFSCRIPTS=.;$TEXMF/tex/{context,plain/base,generic,}//;$TEXMF/scripts/context//
>>
>> and I strongly suspect both are needed. After adjusting the value(s),
>> you will have to rerun luatools --generate.
> 
> I modified texmf.cnf to give these variables those values, but I still
> get the same error, even after luatools --generate.  Further
> suggestions?

Maybe

   $ env MPX_INPUT_TRACE=3 context ...

will give some hint about what mtxrun is doing.

> By the way, I initially modified the "local" texmf.cnf file
> 
>   texlive/2008/texmf.cnf
> 
> rather than the "gloal" configuration file
> 
>   texlive/2008/texmf/web2c/texmf.cnf
> 
> because the former file says that it should contain changes to the
> latter:
> 
>   <---snip--->
>   % If you want to configure something to a value different then the one 
>   % in texmf/web2c/texmf.cnf, just put the changed value here.
>   <---snip--->
> 
> But I noticed that when I ran luatools --generate, it apparently ignored
> this "local" texmf.cnf file; it read only the "global" texmf.cnf file.

This seems to be a difference of opinion between luatools and kpathsea,
(luatools should probably be adjusted to behave the same as kpathsea).

> I inferred that from the output:
> 
>   LuaTools | error unable to locate texmfcnf.lua
>   LuaTools | loading /usr/local/texlive/2008/texmf/web2c/texmf.cnf
>   LuaTools | preparing configuration for /Users/alama/luatex-cache/context/79597d0cc507e8e510dd517f8850b2ca/trees/ae181585be5454a57ae25fb95c3ccbef.tma
>   LuaTools | saving configuration in /Users/alama/luatex-cache/context/79597d0cc507e8e510dd517f8850b2ca/trees/ae181585be5454a57ae25fb95c3ccbef.tma
>   LuaTools | compiling configuration to /Users/alama/luatex-cache/context/79597d0cc507e8e510dd517f8850b2ca/trees/ae181585be5454a57ae25fb95c3ccbef.tmc
>   ...etc.
> 
> Thus I modified the "global" configuration file instead.  By the way,
> the variables LUAINPUTS and TEXMFSCRIPTS already had values:
> 
>   LUAINPUTS = .;$TEXMF/scripts/{$progname,$engine,}/lua//;$TEXINPUTS
>   TEXMFSCRIPTS = $TEXMF/scripts/{$engine,$progname,}//
> 
> But I overwrote those to give them the values you recommended, to no
> avail, unfortunately.
> 
> Jesse
> 

Best wishes,
Taco
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2008-07-03  9:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-02  2:06 Jesse Alama
2008-07-02  7:56 ` Taco Hoekwater
2008-07-03  1:05   ` Jesse Alama
2008-07-03  9:18     ` Taco Hoekwater [this message]
2008-07-04  3:42       ` Jesse Alama
2008-07-04  4:16         ` Aditya Mahajan
2008-07-04 19:40           ` Jesse Alama
2008-07-04 20:32             ` Hans Hagen
2008-07-04 21:41               ` Jesse Alama
2008-07-04 22:17                 ` Hans Hagen
2008-07-05  1:17                   ` Jesse Alama
2008-07-05  7:17           ` Taco Hoekwater
2008-07-06 20:55             ` Jesse Alama
2008-07-07  4:55               ` Jesse Alama
2008-07-07  5:53                 ` Jesse Alama

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=486C997E.4090503@elvenkind.com \
    --to=taco@elvenkind.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).