>|> Lua scripts are already written and in use. Check out >|> >|> musixtex/scripts/musixtex/musixtex.lua >|> pmx/scripts/pmx/pmx.lua >|> mtx/scripts/mtx/mtx.lua >|> >|> in >|> >|> http://mirrors.ctan.org/macros/musixtex/musixtex-texmf.zip >|> http://mirrors.ctan.org/support/pmx/pmx-texmf.zip >|> http://mirrors.ctan.org/support/mtx/mtx-texmf.zip >|> >|> respectively. I hesitate to change their names now but will do so if >|> there's general agreement. They're typically used via symbolic links >|> (on Unix-like systems) or .bat wrapper scripts on Windows, which can of >|> course be named anything a user desires. >| >|As long as they are .lua, the arguments in my post don't apply. But >|there _is_ something self-explanatory about the name 'mtx2pdf' which >|the name 'mtx', even if it is 'mtx.bat', does not convey.
Yes, but all of my scripts have options that allow processing to *stop* at dvi or, for mtx and pmx, at tex (and midi) or, for mtx, at pmx. I often stop at dvi because xdvi works well enough on Postscript slurs and works better than any pdf viewer over a network. Bob ------------------------------- [email protected] mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
