lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Patch for LaTeX lilypond-syntax change


From: Reinhold Kainhofer
Subject: Re: Patch for LaTeX lilypond-syntax change
Date: Tue, 20 Apr 2010 18:31:11 +0200
User-agent: KMail/1.13.2 (Linux/2.6.31-21-generic; KDE/4.4.2; i686; ; )

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Dienstag, 20. April 2010 18:07:50 schrieb Graham Percival:
> > And this back compatibility has no known downsides.
> 
> It makes the lilypond-book code slightly more complicated?  I
> agree that this isn't a big deal.

AFAICS, it's only the regexp that caters for both options before and after 
{lilypond}, so I don't think it's really a complication. We might want to add 
a comment in the code, though, that we kept options before {lilypond} only for 
backward compatibility.


> > I guess if the old syntax is to be deprecated (and it causes problems
> > with LaTeX-aware editors and tools and startles LaTeX users, and
> > _likely_ ), this deprecation needs to be a news
> > item at some point of time.
> 
> I think we'll remove it in lilypond 3.0, as part of the GLISS
> changes.  Granted, this is probably 18 months in the future.

Hmm, with such a time horizon, I'm beginning to think about the \cresc, \dim 
and \decresc text commands again. Shall we really wait that long?

Cheers,
Reinhold
- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, address@hidden, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFLzdbRTqjEwhXvPN0RAsUaAJ9ICPNoI0ClcT62YZr/P5YmUqxZQgCeNyME
7312KJsi13KkFFxRhtqVKMg=
=HT4d
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]