Wolfgang Schuster wrote:

On Sun, Jun 15, 2008 at 9:50 PM, Oliver Buerschaper wrote:

...

Dear all,

is it already possible to run LuaTeX (actually ConTeXt) in batchmode (or nonstopmode) via mtxrun?

Ask such questions next time better on the ConTeXt list.

context --batchmode ... context --nonstopmode ...

Because we're already offtopic I continue with the next question.

Will the "purge" and "purgeall" parameters included in mtx-context or what is there a lua script replacement for "ctxtools --purge --all".

While at it, I would like to place a vote for having as few command names as is feasible. In the current situation I find I often forget whether I need ctxtools or xmltools or textools or ... Best wishes, Taco

Oliver Buerschaper wrote:

...

While at it, I would like to place a vote for having as few command names as is feasible. In the current situation I find I often forget whether I need ctxtools or xmltools or textools or ...

not all scripts are for everyday use ... when using mkiv some can go away (rlxtools may be intergrated in mkiv for instance) but combining all in one also complicstes matters (conflicting flags for instance) some functionality moves ... for instance ctxtools and tmftools contain some 'fixup for tds situations' and that goes away when solved or no longer needed; an example of code that moves from ctxtools to somplace else if pattern conversion code (goes to mtx-patterns) and only an unhappy few will use that (read: mojca and me); in mtx-* featrues are differently organized and grouped other stuff, like texexec's --pdf* features will not end up in mtx-context but will become ctx file driven features, so think of --ctx=pdfcombine and so

I'd second that idea right away!

well, old script will stay forever because mkii will stay forever Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Taco Hoekwater wrote:

Hans Hagen wrote:

...

Oliver Buerschaper wrote:

...

...

While at it, I would like to place a vote for having as few command names as is feasible. In the current situation I find I often forget whether I need ctxtools or xmltools or textools or ...

not all scripts are for everyday use ... when using mkiv some can go away (rlxtools may be intergrated in mkiv for instance) but combining all in one also complicstes matters (conflicting flags for instance)

How about:

$ mtxrun --script whatprovides tpm\* textools --tpmmake $ mtxrun --script whatprovides --all make luatools --make mtxrun --make mtxrun --script context --make mtxrun --script update --make texexec --make $

nice eh? i was thinking of merging luatools and mtxrun but they have too different purposes Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------