lilypond-user
[Top][All Lists]
Advanced

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

Re: Problem with accidentals.ly and Lilypond 2.19.82


From: Luca Danieli
Subject: Re: Problem with accidentals.ly and Lilypond 2.19.82
Date: Thu, 13 Dec 2018 21:03:56 +0000

I have been able to run it!

What it did was to replace the line #(ly:parser-set-note-names parser pitchnames)
with #(ly:parser-set-note-names pitchnames)

So I have got the same problem of before. Some accidentals are replaced with a X. Don't know how to solve it. Am I the only one to have this problem?

Best
Luca

From: lilypond-user <lilypond-user-bounces+address@hidden> on behalf of Luca Danieli <address@hidden>
Sent: 13 December 2018 20:58
To: David Kastrup
Cc: address@hidden
Subject: Re: Problem with accidentals.ly and Lilypond 2.19.82
 
Thank you David.
I tried to you convert-ly, but I got the following error:

>convert-ly: error: accidentals.ly: Unable to determine version.  Skipping

what can I do?

Best
Luca


From: David Kastrup <address@hidden>
Sent: 13 December 2018 13:49
To: Luca Danieli
Cc: address@hidden
Subject: Re: Problem with accidentals.ly and Lilypond 2.19.82
 
Luca Danieli <address@hidden> writes:

> Hi there.
>
> I have got a problem. In my score, I have included the library accidentals.ly
> With Lilypond 2.19.82 I have the error:
>
>
> 163:2<0>: error: GUILE signaled an error for the _expression_ beginning here
>
> #
>
> (ly:parser-set-note-names parser pitchnames)
>
> If I change the line #(ly:parser-set-note-names parser pitchnames)
> with #(ly:parser-set-note-names pitchnames)
>
> the program compiles, but some notes present a X instead of the
> correct accidental.
>
> [cid:b8369fdb-4dc3-4778-96bf-3cf7ffb201d7]
>
> I am stuck between these two things and not know how to solve the
> issues and use accidentals.ly with Lilypond 2.19.82

<http://lilypond.org/doc/v2.18/Documentation/usage/updating-files-with-convert_002dly.en.html>


--
David Kastrup

reply via email to

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