Alexandre Loomis writes:
> Your code is much more readable, but I'm not sure I understand the
> difference between first and second take?
If LilyPond finds that its first attempt of parsing a longer end up with
post-events (those normally attached to a note or rest) in isolation, it
makes a
Your code is much more readable, but I'm not sure I understand the
difference between first and second take?
I just noticed, where I have -3 it is a typo, it should be positive 3
Alex Loomis
On Wed, Jun 7, 2023 at 9:24 AM David Kastrup wrote:
> Alexandre Loomis writes:
>
> > Thanks, that was
Alexandre Loomis writes:
> Thanks, that was very helpful! Adding \tweak padding 1 to the original
> function and defining a continue function by
> nextPed =
> #(define-music-function (end-text) (markup?)
>#{
> \tweak bound-details.left.padding -3
> \startPed "" #end-text
>#})
>
Thanks, that was very helpful! Adding \tweak padding 1 to the original
function and defining a continue function by
nextPed =
#(define-music-function (end-text) (markup?)
#{
\tweak bound-details.left.padding -3
\startPed "" #end-text
#})
makes many cases work or almost work by
Hi Alexandre,
> I'm trying to notate harp pedals
It would be great to have more complete/robust harp pedal support in Lilypond!
> Is there any way to make this more "automatic"?
Unfortunately, I believe TextSpanner still doesn’t implement shorten-pair… but
you can always use padding to fake
Hi all,
I'm trying to notate harp pedals. This should looks something like
[image: mwe1.cropped.png]
I currently have code where it's straightforward to get pretty close, like
this
[image: mwe2.cropped.png]
However, making it look like the first image involves a ton of time
starting the new
