From: Jesse Alama <alama@stanford.edu>
To: ntg-context@ntg.nl
Subject: Re: trouble starting context
Date: Thu, 03 Jul 2008 20:42:30 -0700 [thread overview]
Message-ID: <m2k5g271sp.fsf@stanford.edu> (raw)
In-Reply-To: <486C997E.4090503@elvenkind.com>
Taco Hoekwater <taco@elvenkind.com> writes:
> 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.
$ MTX_INPUT_TRACE=3 context
MtxRun | ! using suffix based filetype: lua
MtxRun | ? blobpath asked: context.lua
MtxRun | ? filename: context.lua
MtxRun | - readable: ./context.lua
MtxRun | ! using suffix based filetype: lua
MtxRun | ? blobpath asked: mtx-context.lua
MtxRun | ? filename: mtx-context.lua
MtxRun | - readable: ./mtx-context.lua
MtxRun | ! using suffix based filetype: lua
MtxRun | ? blobpath asked: mtx-contexts.lua
MtxRun | ? filename: mtx-contexts.lua
MtxRun | - readable: ./mtx-contexts.lua
MtxRun | ! remembered: mtx-context.lua
MtxRun | unknown script: context
It seems that mtxrun has no idea where to look for mtx-context.lua. Any
suggestions?
Thanks,
Jesse
--
Jesse Alama (alama@stanford.edu)
___________________________________________________________________________________
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:[~2008-07-04 3:42 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
2008-07-04 3:42 ` Jesse Alama [this message]
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=m2k5g271sp.fsf@stanford.edu \
--to=alama@stanford.edu \
--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).