Re: The LilyPond syntax for notes

I don't think so. Considering you need a pitch name, a duration, and an octave indication (depending), this syntax is entirely natural and it is no surprise it may occur in many programs. It's a natural idea, spontaneously arising many times. Well, Humdrum predates Lilypond, so your

Re: Chromatic clashes

Hi, in addition to that, I've on occations had to engrave [image: image.png] (on manuscript they are even uglier: [image: image.png], with an added extra stem) which involves a great deal of tweakin moving notes and accidentals. Wouldn't be nice to generate a complete approach to that kind of

Percent repeat signs do not scale correctly with magnifyStaff

Hello all, when using \magnifyStaff it seems as though the dots of a percent repeat sign will scale accordingly, but not the slash. I cannot imagine this is expected behaviour. \version "2.23.2" { \magnifyStaff 0.5 \repeat percent 2 { c'1 } } I also could not find any method to

Chromatic clashes

Folks, while the following musical constellation is ugly in the first place, I think we can agree that LilyPond's rendering is less than ideal: \version "2.22.0" { 4 } yielding If we force an accidental to c, we get something that might have a slightly higher probability of being

The LilyPond syntax for notes

Hello folks, I seem to have read somewhere that the notation such as c’4.. has been inspired by another well-known syntax, maybe refering to Humdrum. Does anyone know more about this? JM

Re: readline for guile

On Thu, Apr 15, 2021 at 5:36 AM Andrew Culver wrote: > > Here is scheme-sandbox.ly that comes with my v2.22 install: > > \version "2.16.0" > > #(load-user-init) > > % This loads the user's .guile file for interactive sessions. > % One typical thing you might want to put there is > % (use-modules

Re: readline for guile

Le 15/04/2021 à 14:32, Andrew Culver a écrit : Here is scheme-sandbox.ly  that comes with my v2.22 install: \version "2.16.0" #(load-user-init) % This loads the user's .guile file for interactive sessions. % One typical thing you might want to put there is %

Re: Accidental placement below accidental-carrying tie

> While not an ideal solution, just killing the (invisible) accidental's > stencil seems to work: > > \version "2.20.0" > > noAccidental = \tweak Accidental.stencil ##f \etc > > \score { >   \new Staff << >     \key a \major \time 4/2 \partial 2 >     \clef "bass" >     << { c'2~ \noAccidental

Re: Accidental placement below accidental-carrying tie

Hi Daniel, What’s up with the placement of the G natural accidental in this example? It seems to make space for the C natural accidental that would have been there, had it not been carried over with the tie. How can I fix this? \version "2.20.0" \score { \new Staff << \key a \major

Re: Accidental placement below accidental-carrying tie

On Fri, 16 Apr 2021 at 14:25, Daniel Tobias Johansen Langhoff < dtlangh...@gmail.com> wrote: > > Hi! > > What’s up with the placement of the G natural accidental in this > example? It seems to make space for the C natural accidental that > would have been there, had it not been carried over with

Accidental placement below accidental-carrying tie

Hi! What’s up with the placement of the G natural accidental in this example? It seems to make space for the C natural accidental that would have been there, had it not been carried over with the tie. How can I fix this? \version "2.20.0" \score { \new Staff << \key a \major \time 4/2