Don Simons wrote: > Glad things have improved somewhat. Soon they'll be perfect. > > I can't say one way or the other without eexperimenting whether a tab in > comment line would cause trouble, but it's safest not to have any tabs at > all. > > Here's the deal with *.mx?: Starting with a clean working folder, when you > run tex the first time, musixtex will generate *.mx1. This serves as input > to musixflx, which then generates *.mx2. Then on the second tex pass, > musixtex uses *.mx2 as input. So how does musixtex know whether it's the > 1st or 2nd pass? By checking for the presence of *.mx1. If not there, it > assumes 1st pass; if there, 2nd. So *.mx1 is the only file that you really > need to delete when you change something in the pmx source file. But of > course that's not to say for good housekeeping you shouldn't delete any > other files before recompiling.
I'm afraid that's not quite correct - MusiXTeX determines which pass it is on based on the .mx2 file, not the .mx1[*]. It attempts to open the .mx2 file each time and if that is missing *then* it overwrites (or creates) the .mx1 file. So the file you have to delete is in the fact .mx2 file (try doing tex musixdoc - musixflx musixdoc - del musixdoc.mx1 - tex musixdoc and you'll see...) Technically speaking you only need to regenerate the .mx2 file if the spacing of the bars has altered (so correcting a note, for example, doesn't need it) but in practice you just delete it every time as it doesn't like as long to run musixflx as I think it did when it was first written! David [*] Unless that's changed since T.112 as I'm still a bit out-of-date on my system... _______________________________________________ [email protected] mailing list If you want to unsubscribe or look at the archives, go to http://mailman.nfit.au.dk/mailman/listinfo/icking-music-archive.org-tex-music
