Hans can give a more authoritative answer, of course, but as a provisional one: no, the command name hasn't changed, you don't need to worry. The way ConTeXt is organized is that the binary texexec (which resides in texmf/ARCH/bin/) is just a small shell-script, a stub, that calls the real script in turn. This has been texexec.pl (in texmf/scripts/context/perl/), but you can of course modify it so it runs another script. Hans has been toying with ruby lately, so we now have texmf/scripts/ruby/newtexexec.rb which, I suppose, will replace the "old" texexec in due time. But as you have seen, it's not yet quite ready for prime time, it's still missing a few features (I don't think it can post-process pdf-files yet) and has a few buglets... So relax and vatch das blinkenlight! All best Thomas On Nov 10, 2005, at 9:33 AM, Gerben Wierda wrote:
Correction: I goofed up; after correcting the file, I get exactly what I expected. AFAICS, index generation now works flawlessly with newtexexec! Great, wonderful, kudos to you!
Um, I just noticed. "newtexexec"? Has the command name changed? Please say no. Because a command name change would mean that I have to redistribute the binaries (where the command lives) and not just the context trees in texmf.
G
_______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context