From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: John Kitzmiller <jkitzm@gmail.com>
Subject: Re: Lua script not registered
Date: Fri, 02 Dec 2011 23:46:28 +0100 [thread overview]
Message-ID: <4ED95544.3030509@wxs.nl> (raw)
In-Reply-To: <CAHYz2AVwwp56o8w-p9UZbVrPhScWQfBuWk+57OWA0vTM_8_ZKQ@mail.gmail.com>
On 2-12-2011 23:42, John Kitzmiller wrote:
> I hope this does not open another thread with the same name, but I did not
> find a way to respond directly within the archive--something else I am
> missing or will ntg find the reference? Here it goes...
>
> Thank you for response luigi. The story:
>
> OS = Windows7 professional
> I also have MikTeX installed which I use routinely for pdfLaTeX and
> METAPOST from TeXworks
>
> download context-setup-mswin.zip<http://minimals.contextgarden.net/setup/context-setup-mswin.zip>
> from
> the wiki
> unzip to C:\context
> run from shell C:\context>first-setup.bat --modules=all
> add to PATH C:\context\tex\texmf-mswin\bin\
> run from shell C:\context>first-setup.bat --keep
>
> Then create tex file \starttext Hello world \stopptext in different
> location.
>
> Navigate shell to that location and>context firstfile.tex
>
> Result is message
> context: The Lua script is not registered.
> context: Data: context
>
> Aha! I tried moving firstfile.tex into C:\context and then run and it
> works, but takes 11.62 seconds--not so good.
Each run? On my (over 5 years old) machine a Hello world takes less than
a second.
> However, I still get Lua script not registered when I try to run from other
> file locations, which makes me think it is PATH problem that I will
> continue to chase but if anything looks obvious please help.
Can you install the standalone distribution from the garden and see if
that one works?
Hans
-----------------------------------------------------------------
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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-12-02 22:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 22:42 John Kitzmiller
2011-12-02 22:46 ` Hans Hagen [this message]
2011-12-02 23:36 ` Aditya Mahajan
-- strict thread matches above, loose matches on Subject: below --
2011-12-03 16:55 John Kitzmiller
2011-12-03 3:56 John Kitzmiller
2011-12-03 9:30 ` Mojca Miklavec
2011-12-03 10:52 ` Hans Hagen
2011-12-03 11:05 ` luigi scarso
2011-12-02 16:04 John Kitzmiller
2011-12-02 16:29 ` luigi scarso
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=4ED95544.3030509@wxs.nl \
--to=pragma@wxs.nl \
--cc=jkitzm@gmail.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).