> Date: Wed, 03 Mar 1999 09:09:00 +0100
> From: Christian Mondrup <[EMAIL PROTECTED]>
> Van Ryckeghem Andr e' wrote:
> > echo %1 | pmxa
> > echo %1 | pmxa >%1_pmxa.log
The first line should be removed.
The second line can be improved for most un*xes or if you have e.g. 4DOS:
echo %1 | pmxa | tee %1_pmxa.log
Now the terminal output of pmxa goes to the screen _and_ to the log-file.
Same for pmxb.
> > C:\musixtex\musixflx %1.tex
If you are interested in as many log-files as possible (:-), you may
request a musixflx log-file <jobname>.mxl by appending " f" at the command
line. The disadvantage is that the extended output goes to the screen, too
and that it is required to acknowlege it.
> > C:\gstools\gsview\gsview32.exe %1.ps
>
> Why don't you just use the exellent MiKTeX previewer yap ? If you keep the
> yap window open the current dvi file will be refreshed each time it is
> generated anew.
The same is true for newer versions of gsview as well as for the stone-old
versions of dviwin and dviwin2
My procedures for PMX and MusiXTeX are seperate definitions and PMX calls
MusiXTeX. The same is true for my M-Tx procedure which calls the seperate
PMX (which calls MusiXTeX).
My MusiXTeX procedure has a parameter n which allows to call only the
3rd phase without deleting .mx2. For small changes which do not influence
the music layout this is faster. I use it too, for most of my bigger
publications, to be aware, if a small source change results in a big layout
change - which often needs some additional manual optimization e.g. to
insert some space in front of accidentals (which is automagically done
by PMX).
