Le 30/12/2021 à 23:04, Lukas-Fabian Moser a écrit :
Hi Jean,
Both of these cases seem to work the same as in
current versions if I do
[...]
SCM
assq_tail (SCM key, SCM alist, SCM based_on = SCM_EOL)
{
- for (SCM p = alist; !scm_is_eq (p, based_on); p = scm_cdr (p))
+ for (SCM p =
Hi Jean,
Both of these cases seem to work the same as in
current versions if I do
[...]
SCM
assq_tail (SCM key, SCM alist, SCM based_on = SCM_EOL)
{
- for (SCM p = alist; !scm_is_eq (p, based_on); p = scm_cdr (p))
+ for (SCM p = alist; scm_is_pair (p) && scm_is_pair (scm_car (p)) &&
Le 30/12/2021 à 12:36, Lukas-Fabian Moser a écrit :
It's much worse than that: It's not the first time _I've_ been tripped
up by this (previously it was with sort!). I'll just have to write 100
copies of
"The exclamation mark in something! does not mean the function is
guaranteed to make the
Hi Jean, (CCing devel because of the stuff below the asterisks)
Although this approach manipulates internal data structures of
LilyPond, it has the advantage of dealing with your issue at the root
and not causing side effects for other scripts. Unfortunately, this
approach does not work
Le 29/12/2021 à 09:45, Lukas-Fabian Moser a écrit :
A cleaner and more surgical solution would be:
\version "2.18"
#(assoc-set! (assoc-ref default-script-alist "tenuto") 'padding 0.5)
\new Staff {
\relative c'' {\time 3/4 a g e--}
}
Although this approach manipulates internal data
Thank you for all the answers! The solution that best suits my situation is
overriding the script.padding, what Vaughan suggested. I find the staccatos to
be too close to notes as well, so having it affect all articulations doesn't
seem like a problem (at least at the moment). As Lukas pointed
Hello Erika,
the problem here is that Lilypond handles many Articulations the same way. So
overriding Script.padding will affect all articulations.
We have recently discussed possibilites to override properties for specific
articulations, but if you are using the shorthand -- for tenuto then
Hi Erika,
I would like to have the tenuto mark a bit farther away from the note.
I had a similar issue with tuplet numbers and then "\override
TupletNumber.Y-offset = #-2.5" fixed the issue. I don't know what I
should replace "TupletNumber" by in the case of tenuto lines.
Minimal example
> I would like to have the tenuto mark a bit farther away from the
> note. I had a similar issue with tuplet numbers and then "\override
> TupletNumber.Y-offset = #-2.5" fixed the issue. I don't know what I
> should replace "TupletNumber" by in the case of tenuto lines.
Have a look at this
On Wed, 29 Dec 2021 at 12:48, Erika Pirnes wrote:
>
> Hi,
>
> I would like to have the tenuto mark a bit farther away from the note. I
had a similar issue with tuplet numbers and then "\override
TupletNumber.Y-offset = #-2.5" fixed the issue. I don't know what I should
replace "TupletNumber" by
Hi,
I would like to have the tenuto mark a bit farther away from the note. I had a
similar issue with tuplet numbers and then "\override TupletNumber.Y-offset =
#-2.5" fixed the issue. I don't know what I should replace "TupletNumber" by in
the case of tenuto lines.
Minimal example here:
11 matches
Mail list logo
