ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: trouble starting context
Date: Fri, 4 Jul 2008 00:16:04 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.1.00.0807040015000.5656@nqv-yncgbc> (raw)
In-Reply-To: <m2k5g271sp.fsf@stanford.edu>

On Thu, 3 Jul 2008, Jesse Alama wrote:

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

What does  MPX_INPUT_TRACE=3 luatools --generate say?

Aditya
___________________________________________________________________________________
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-04  4:16 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
2008-07-04  4:16         ` Aditya Mahajan [this message]
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=alpine.DEB.1.00.0807040015000.5656@nqv-yncgbc \
    --to=adityam@umich.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).