> Thomas Ruedas skryf:
> > BTW, is there a conflict between MusiXTeX and certain commands of the
> > amsmath package?
>
> The only way to find out is the hard way. You're supposed to code
> \newcommand or \renewcommand instead of \def (except when the command
> name contains an @ sign) so that all conflicts are found at the TeX
> stage.
there's nothing in the guidelines that says you needn't use
\newcommand or whatever for internal commands.
> But MusiXTeX is not in LaTeX, and amsmath.sty uses the pure
> LaTeX commands only 30 times and plain \def on user-visible commands
> 41 times.
there's the rub: amsmath _is_ (in effect) part of latex -- it's
distributed from the required subdirectory, and the principal author
is part of the latex team.
> The first 30 commands can be checked by \usepackage{musixtex,amsmath}.
> The remaining 41 cases need to be done manually.
of course one can't hope that musixtex would care to use the latex
commands, since its use in the context of latex is something of a
minority sport (i've always assumed). but it might be nice if
musixtex were to check for clashes using a mechanism of its own...
robin
(not speaking for the latex team...)
