Re: Replacement for "parser"

[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.


> On 30 Jul 2016, at 16:48, David Kastrup <address@hidden> wrote:
> 
> convert-ly tends to have an answer for most questions like that.


Urs Liska already gave the answer in private email:

Use (*parser*) (and (*location*)).