On Sun, 2024-12-22 at 16:41 +, Mark Knoop wrote:
>
>
> At 15:04 on 22 Dec 2024, Richard Shann wrote:
> > On Sun, 2024-12-22 at 12:04 +, Richard Shann wrote:
> > > On Sun, 2024-12-22 at 11:51 +, Richard Shann wrote:
> > > > Is there a neat way to start a glissando mark further from the
At 15:04 on 22 Dec 2024, Richard Shann wrote:
> On Sun, 2024-12-22 at 12:04 +, Richard Shann wrote:
>> On Sun, 2024-12-22 at 11:51 +, Richard Shann wrote:
>> > Is there a neat way to start a glissando mark further from the note
>> > than the default?
>> I've found it - sorry:
>>
>> \once
On Sun, 2024-12-22 at 12:04 +, Richard Shann wrote:
> On Sun, 2024-12-22 at 11:51 +, Richard Shann wrote:
> > Is there a neat way to start a glissando mark further from the note
> > than the default?
> I've found it - sorry:
>
> \once\override Glissando.bound-details.left.padding = #2.5
I
On Sun, 2024-12-22 at 11:51 +, Richard Shann wrote:
> Is there a neat way to start a glissando mark further from the note
> than the default?
I've found it - sorry:
\once\override Glissando.bound-details.left.padding = #2.5
Richard
> I see a property called ly:line-spanner::calc-left-
> bou
Is there a neat way to start a glissando mark further from the note
than the default? I see a property called ly:line-spanner::calc-left-
bound-info but no examples of its use.
Richard Shann
(The composer wants to use this to indicate that the glissando doesn't
start straight away, instead the not
