-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 23 August 2009 02:16:15 Carl Sorensen wrote: > On 8/22/09 5:13 PM, "Graham Percival" <gra...@percival-music.ca> wrote: > > If this change uses \newcr or \crnew or whatever, then fine. If > > it redefines the behavior of \cresc, then I recommend caution. > > Yes, we should call it \newcresc, and indicate in the documentation > that \cresc is deprecated.
I absolutely don't like having New* stuff, since (1) this requires anyone using it early to adjust the syntax later on again and (2) it suggests that this is either something super-duper-great or experimental, which is both not true. It's rather just the problem that the existing syntax shouldn't be changed for now. So,for now I would simply apply that patch so that the properties get interpreted, but don't add a new command, which will be changed in the next version again. Anyone who whats to use them (basically, that's me for now),can always write our own mycresc or even overload the existing cresc command as postfix. Cheers, Reinhold - -- - ------------------------------------------------------------------ Reinhold Kainhofer, Vienna University of Technology, Austria email: reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/ * K Desktop Environment, http://www.kde.org, KOrganizer maintainer * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFKkYMZTqjEwhXvPN0RAkZuAJ9M946WrsqKfZeulCWZPFbwuc7WZgCfVZjn QGgpffQTe2CKf8RzmrdRWKg= =cjxr -----END PGP SIGNATURE----- _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
