Happy New Year
Today I tried both the 32 bit and the 64-bit versions of version
2.12.1-1, but still producing the unwanted filename.
Could the answer lie in the language settings on this debian-box?
(excerpts of set and env):
MM_CHARSET=ISO-8859-1
SHELL=/bin/bash
LANG=da_DK
codesite-noreply wrote:
I expect my music to be compatible and readable. In stead I receive an
error saying that ≤ syntax error, unexpected DIGIT
\version
2.12.0 % necessary for upgrading to future LilyPond versions.
≥
In your code you wrote
Markup
instead of
On 1/1/09 5:01 PM, codesite-nore...@google.com
codesite-nore...@google.com wrote:
Comment #2 on issue 719 by gpermus: New Version statement not accepted
http://code.google.com/p/lilypond/issues/detail?id=719
sineneg1,
You quoted a message telling you NOT to add material directly to
James E. Bailey wrote:
Apparently lilypond is a little too smart with delayed ties.
Is this perhaps even worth a bug report?
/Mats
You have a ~ in the first measure which isn't completed until the
third measure. Get rid of it, and you should have what you want.
Am 02.01.2009 um 21:12
Am 02.01.2009 um 23:46 schrieb Mats Bengtsson:
James E. Bailey wrote:
Apparently lilypond is a little too smart with delayed ties.
Is this perhaps even worth a bug report?
The one thing I've learned with lilypond is that I don't know what a
bug is.
On Fri, Jan 02, 2009 at 10:55:15AM -0700, Carl D. Sorensen wrote:
I'd suggest that the warning be changed to
Please DO NOT add issues directly to this tracker unless
you have received permission to do so. Instead, send an
email to bug-lilypond@gnu.org with the following information:
Hello!
I have noticed something strange, looks like a bug
with producing midi files for piano pieces.
It appears in lilypond 2.11.61 and 2.12.1 built from sources for 64-bit linux
and lilypond 2.12.1 from the binary linux-x86_64 distribution.
Everything was OK in old lilypond-2.11.0 (but using
