From: Michael Green <merely.ridiculous@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: Unable to generate luatex formats
Date: Mon, 14 Apr 2008 22:43:47 -0700 [thread overview]
Message-ID: <576B114A-BE98-459A-A809-8ACB8A727294@gmail.com> (raw)
The two files Taco pointed to *appear* to be OK (though I'm too
inexperienced to say with certainty). That leaves something esoteric
or a tossed salad of old and new code.
Since this is mainly a matter of learning and curiosity for me, I'll
wait and see how things develop for a bit.
Thanks for your help!
mjg
>> I think either
>>
>> /usr/local/texlive/texmf-local/tex/context/base/luat-env.tex
>>
>> is not the one from the latest context distribution, or an extra
>> luatools --generate command is needed.
>>
>> You can check the \contextversion by looking at
>>
>> /usr/local/texlive/texmf-local/tex/context/base/context.tex
>>
>> around line 45, it should say
>>
>> \edef\contextversion{2008.04.11 14:48}
>>
>>
>> There can be some more esoteric causes, but these are the two most
>> likely ones.
>>
>
> in previou sversions the env was loaded runtime (this behaviour
> originated in the stepwise development of embedding bytecodes in the
> format, in the beginning all chunks were loaded at runtime); i managed
> to get rid of that; in addition to taco's suggestions ... so it
> could be
> that old code and new code is mixed.
___________________________________________________________________________________
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 reply other threads:[~2008-04-15 5:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 5:43 Michael Green [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-15 16:10 Michael Green
2008-04-12 20:53 Michael Green
2008-04-13 8:02 ` Taco Hoekwater
2008-04-13 11:54 ` Hans Hagen
2008-04-13 10:12 ` Jean Magnan de Bornier
2008-04-15 7:57 ` John Devereux
2008-04-15 9:31 ` Taco Hoekwater
2008-04-15 9:44 ` John Devereux
2008-04-15 9:56 ` Hans Hagen
2008-04-15 10:37 ` John Devereux
2008-04-15 10:46 ` Mojca Miklavec
2008-04-15 11:25 ` John Devereux
2008-04-15 12:17 ` Mojca Miklavec
2008-04-15 12:52 ` John Devereux
2008-04-15 12:59 ` Mojca Miklavec
2008-04-16 15:18 ` John Devereux
2008-04-16 18:29 ` Mojca Miklavec
2008-04-15 14:16 ` Hans van der Meer
2008-04-15 14:29 ` Mojca Miklavec
2008-04-15 14:31 ` Mojca Miklavec
2008-04-15 15:00 ` Hans Hagen
2008-04-15 10:40 ` Hans van der Meer
2008-04-15 9:43 ` Mojca Miklavec
2008-04-16 10:21 ` John Devereux
2008-04-16 18:53 ` Joel C. Salomon
2008-04-16 19:01 ` Mojca Miklavec
2008-04-16 20:32 ` Hans Hagen
2008-04-17 4:55 ` Joel C. Salomon
2008-04-17 7:50 ` Taco Hoekwater
2008-04-17 8:03 ` Hans Hagen
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=576B114A-BE98-459A-A809-8ACB8A727294@gmail.com \
--to=merely.ridiculous@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).