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: Sat, 03 Dec 2011 11:52:11 +0100 [thread overview]
Message-ID: <4ED9FF5B.5030308@wxs.nl> (raw)
In-Reply-To: <CAHYz2AUOjLSRxNVXmpz3jwbiyAt8b413CSiXT+W7ZR=P3UYQjA@mail.gmail.com>
On 3-12-2011 04:56, John Kitzmiller wrote:
> Replying to the list in this manner--having to retype the subject--is
> unusual to me, and I hope it does not create problems for the list. Please
> help me on how to reply within the mail archive to make more efficient.
> Many thanks to those who have replied on the topic!
>
> Thank you, Aditya--
>
> I had run C:\context\tex\setuptex.bat and then tried
>
> C:\context>context firstfile.tex
>
> which worked (now down to 3+ secs from 11+ at first run--file = \starttext
> Hello World \stoptext)
>
> I think I can get this setuptex.bat automated for random context runs but,
>
> for some reason(s) C:>context somefile.tex will not work globally on my
> personal computer (Lenovo x100e) over which I have admin control (maybe I
> am not a good admin?) and I have added C:\context\tex\texmf-mswin\bin to my
> PATH
>
> I still get "Lua script not registered" complaint when I try to compile
> outside of C:\context directory
>
> I suppose I could live with keeping all binaries and docs in C:\context,
> but that is not so inviting compared to being able to pdfLaTeX a doc over
> Dropbox via MikTeX for example.
I use windows here and it works ok, so it should be possible to get it
working. In principle the only thing needed is to add the tex bin path
to the environment variable PATH (beware there are two of them). From an
editor, you can best run 'mtxrun --script context ...'.
Is the cache generated? Has there been an initial 'mtxrun --generate'?
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-03 10:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 3:56 John Kitzmiller
2011-12-03 9:30 ` Mojca Miklavec
2011-12-03 10:16 ` OT: Replying to messages from archive (was: Lua script not registered) Paul Menzel
2011-12-03 10:52 ` Hans Hagen [this message]
2011-12-03 11:05 ` Lua script not registered luigi scarso
-- strict thread matches above, loose matches on Subject: below --
2011-12-03 16:55 John Kitzmiller
2011-12-02 22:42 John Kitzmiller
2011-12-02 22:46 ` Hans Hagen
2011-12-02 23:36 ` Aditya Mahajan
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=4ED9FF5B.5030308@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).