> On 30 Jul 2016, at 19:09, Urs Liska wrote:
>> Looking at the file I am actually using (with SMuFL glyphs), (*parser*)
>> is not needed, but Graham’s file regular.ly has a line
>> retune = #(define-music-function (parser location ET midc m)
>> (rational? integer? ly:music?) m)
>>
>
> That's
> On 30 Jul 2016, at 15:47, Malte Meyn 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
> On 30 Jul 2016, at 19:09, Urs Liska wrote:
>> Looking at the file I am actually using (with SMuFL glyphs), (*parser*)
>> is not needed, but Graham’s file regular.ly has a line
>> retune = #(define-music-function (parser location ET midc m)
>> (rational? integer? ly:music?) m)
>>
>
> That's
Malte Meyn writes:
> Am 30.07.2016 um 18:30 schrieb Hans Åberg:
>>
>>> On 30 Jul 2016, at 18:21, Malte Meyn wrote:
>>
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.
>>
>
Am 30. Juli 2016 18:30:57 MESZ, schrieb "Hans Åberg" :
>
>> On 30 Jul 2016, at 18:21, Malte Meyn wrote:
>
>>> 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.
>
>Looking at the fi
Hans Åberg writes:
>> On 30 Jul 2016, at 18:21, Malte Meyn wrote:
>
>>> 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.
>
> Looking at the file I am actually using (with SMuFL g
Am 30.07.2016 um 18:30 schrieb Hans Åberg:
On 30 Jul 2016, at 18:21, Malte Meyn wrote:
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.
Looking at the file I am actually usi
> On 30 Jul 2016, at 18:21, Malte Meyn wrote:
>> 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.
Looking at the file I am actually using (with SMuFL glyphs), (*parser*) is not
Am 30.07.2016 um 18:06 schrieb Hans Åberg:
On 30 Jul 2016, at 15:47, Malte Meyn 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.
Hans Åberg writes:
> 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 = #…
> Unbo
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
newgl
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 vari
12 matches
Mail list logo
