Re: glissando lines and accidentals

2020-08-11 Thread Kevin Barry
> By the way, do you agree that this is a bug in LilyPond? Gould suggests it is: the example on page 143 in my edition of Behind Bars, from a Bartok string quartet, shows only the glissando lines that run into an accidental getting shortened (in fact, when there are enough accidentals that there a

Re: glissando lines and accidentals

2020-08-11 Thread Werner LEMBERG
> By the way, do you agree that this is a bug in LilyPond? I just want to mention that Aaron's solution doesn't work in general if more than two notes are involved in the chord. For a good solution, the horizontal skylines of the involved chords have to be taken into account; the lengths of the

Re: glissando lines and accidentals

2020-08-11 Thread Werner LEMBERG
> Here is a theoretically better version of the code, along with an > improved test case so that the slopes are more easily compared: Aaron, you are a wizard! My deepest respects for your Scheme skills. Thanks a lot! Again, this deserves to become a lilypond snippet. By the way, do you agree

Re: glissando lines and accidentals

2020-08-11 Thread Aaron Hill
On 2020-08-11 5:05 am, Aaron Hill wrote: On 2020-08-11 3:43 am, Werner LEMBERG wrote: Very nice, thanks! The only thing now is to get the two lines parallel, which looks like a lot of additional work... Oof... I am almost certainly overlooking something easier, but this appears to work:

Re: glissando lines and accidentals

2020-08-11 Thread Aaron Hill
On 2020-08-11 3:43 am, Werner LEMBERG wrote: { 2\glissando } Due to the flat, the lower glissando line is far too short. beyond my capabilities right now. Is there a solution to circumvent this temporarily? \version "2.20.0" { \override Glissando.before-line-breaking = #(lambda

Re: glissando lines and accidentals

2020-08-11 Thread Werner LEMBERG
>> { 2\glissando } >> >> Due to the flat, the lower glissando line is far too short. >> >> beyond my capabilities right now. Is there a solution to >> circumvent this temporarily? > > > \version "2.20.0" > > { > \override Glissando.before-line-breaking = > #(lambda (grob) > (le

Re: glissando lines and accidentals

2020-08-11 Thread Aaron Hill
On 2020-08-11 2:15 am, Werner LEMBERG wrote: Folks, look at this example: { 2\glissando } Due to the flat, the lower glissando line is far too short. I consider this a bug. LilyPond already provides the `end-on-accidental` property (which is set to #t by default). For chords, however, t

glissando lines and accidentals

2020-08-11 Thread Werner LEMBERG
Folks, look at this example: { 2\glissando } Due to the flat, the lower glissando line is far too short. I consider this a bug. LilyPond already provides the `end-on-accidental` property (which is set to #t by default). For chords, however, this should be only applied to glissando lines