[Top][All Lists]

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

Re: Syntax error in ranged tempo specifications

From: Federico Bruni
Subject: Re: Syntax error in ranged tempo specifications
Date: Sun, 22 Sep 2013 11:42:01 +0200

2013/9/22 Joachim Mairböck <address@hidden>

> The syntax of a ranged tempo specification changed from \tempo <dur> =
> <low>
> ~ <high> to \tempo <dur> = <low> - <high> from version 2.16 to current
> unstable, i.e. it uses a '-' instead of a '~'.
> This is a good change. However, a source file containing a statement like
> this and \version "2.16.0" doesn't compile using the current unstable
> version. The \version command should enable compatibility with older
> versions (and Lilypond should accept both forms if such a \version
> statement
> exists).
Hi Joachim

the \version statement is useful for convert-ly to update to the new syntax.
But convert-ly can only upgrade the syntax; downgrade is not possible. This
has been recently added explicitely in the documentation of 2.17.27 (to be
released in the next days):

So if you have this file:

\version "2.16.2"

  \tempo 4 = 40 ~ 46
  c4. e8 a4 g
  b,2 d4 r

you can run convert-ly in order to use it with the latest development
But once you've update to the new syntax, you cannot go back to the older
You should use a control version system like Git or Mercurial for this sort
of stuff.

Hope it helps

reply via email to

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