Re: Replacement for "parser"

> 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

Re: Replacement for "parser"

> 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

Re: Dynamic with markup text function

Hello Dimitris, What would you like to align the dynamics with? JM > Le 29 juil. 2016 à 20:44, dtsmarin a écrit : > > Yes!! > Thanks a lot! > What about the alignment? Is it configurable like the other default objects? > > > > > > -- > View this message in context: > http://lilypond.1069

Re: Replacement for "parser"

> 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

Re: Replacement for "parser"

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

Re: Replacement for "parser"

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

Re: Replacement for "parser"

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

Re: Replacement for "parser"

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

Re: Replacement for "parser"

> 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

Solved (Re: How to set the beam positions manually?)

Andrew Bernard wrote: > Provide a minimal working example we can see. Thank you so much for your interest in this problem, finally i could solve it like this. \once\override Beam.positions = #'(-1 . -2.8) d16 [g,] \once\override Beam.positions = #'(1 . -1)\stemUp g8\stemDown d' | \once\override

Re: Replacement for "parser"

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.

Re: Replacement for "parser"

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

Re: Replacement for "parser"

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

Replacement for "parser"

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

Re: Adding a tempo indication in the middle of multiple voices mode

Stephen Cox writes: > I want to add a tempo indication in the middle of some code that is in > multiple voices mode. > > For instance, using the example on page 48 of the “Learning” document, I > might want to add the indication “Faster” at the beginning of bar 2. The code > below in a file tr

Re: Adding a tempo indication in the middle of multiple voices mode

On 30/07/16 10:36, Stephen Cox wrote: > I want to add a tempo indication in the middle of some code that is in > multiple voices mode. > > For instance, using the example on page 48 of the “Learning” document, I > might want to add the indication “Faster” at the beginning of bar 2. The > code belo

Re: Adding a tempo indication in the middle of multiple voices mode

r4 g g4. a8 ^\markup{Faster} | -- Phil Holmes - Original Message - From: Stephen Cox To: lilypond-user@gnu.org Sent: Saturday, July 30, 2016 10:36 AM Subject: Adding a tempo indication in the middle of multiple voices mode I want to add a tempo indication in the middle

Adding a tempo indication in the middle of multiple voices mode

I want to add a tempo indication in the middle of some code that is in multiple voices mode. For instance, using the example on page 48 of the “Learning” document, I might want to add the indication “Faster” at the beginning of bar 2. The code below in a file try.ly gives the e