lilypond-user
[Top][All Lists]
Advanced

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

Re: Replacement for "parser"


From: Malte Meyn
Subject: Re: Replacement for "parser"
Date: Sat, 30 Jul 2016 18:21:34 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0



Am 30.07.2016 um 18:06 schrieb Hans Åberg:

On 30 Jul 2016, at 15:47, Malte Meyn <address@hidden> wrote:

Am 30.07.2016 um 14:53 schrieb Hans Åberg:
When using Graham Breed’s regular.ly, one writes a line like
 #(ly:parser-set-note-names parser SomePitchNames)
which worked in LilyPond 2.19.10. But in 2.19.45, there is an error:
error: GUILE signaled an error for the expression beginning here
newglyphs = #…
Unbound variable: parser

So the variable “parser” does not exist anymore, it seems. What is the 
replacement?

There is none. Just omit it like “parser location” in define-music-function.

#(ly:parser-set-note-names SomePitchNames)

This is what convert-ly does ;)

That one, I discovered, but “parser” must be there in another location.
Are you sure? input/regression/note-names.ly doesn’t have parser or (*parser*) anywhere.



reply via email to

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