Lovely, thank you Knute
L
On Mon, 20 Nov 2023, 16:11 Knute Snortum, wrote:
> On Mon, Nov 20, 2023 at 6:34 AM Luca Fascione
> wrote:
>
>> Did this change between 22 and 24?
>> Is there somewhere I can go to see the implementation for the LSR that
>> used 2.22?
>>
>> L
>>
>> On Mon, 20 Nov 2023,
On Mon, Nov 20, 2023 at 6:34 AM Luca Fascione wrote:
> Did this change between 22 and 24?
> Is there somewhere I can go to see the implementation for the LSR that
> used 2.22?
>
> L
>
> On Mon, 20 Nov 2023, 15:07 Knute Snortum, wrote:
>
>> On Mon, Nov 20, 2023 at 4:35 AM Luca Fascione
>> wrote:
It's for a chord symbol in ChordName mode (Ab7, say)
I didn't think those supported arpeggio brackets
L
On Mon, 20 Nov 2023, 15:39 Ben Bradshaw, wrote:
> As an alternate approach could you use the \arrpegioBracket ? It's a
> little more square, but I think there's a way to override that. I use
As an alternate approach could you use the \arrpegioBracket ? It's a little
more square, but I think there's a way to override that. I used it once to
put a bracket around a cord. You just have to override one of the
properties to move the endpoints in the negative direction as well as an x
offset
Did this change between 22 and 24?
Is there somewhere I can go to see the implementation for the LSR that used
2.22?
L
On Mon, 20 Nov 2023, 15:07 Knute Snortum, wrote:
> On Mon, Nov 20, 2023 at 4:35 AM Luca Fascione
> wrote:
>
>> Also,
>> it doesn't seem to actually work on 2.22 (see below)
>>
On Mon, Nov 20, 2023 at 4:35 AM Luca Fascione wrote:
> Also,
> it doesn't seem to actually work on 2.22 (see below)
>
> How does this even compile on the LSR?
>
The LSR uses LilyPond 2.24.2, which compiles the source without error.
--
Knute Snortum
Also,
it doesn't seem to actually work on 2.22 (see below)
How does this even compile on the LSR?
https://lsr.di.unimi.it/LSR/Snippet?id=902
L
===
\version "2.22.2"
startParenthesis = {
\once \override Parentheses.stencils = #(lambda (grob)
(let ((par-list (parentheses-interf
Yes, I was thinking more about parenthesizing say a chord or a scale,
rather than a head vs a flat/sharp sign.
I think that next to a chord (say 8) I'd want parentheses around the
heads, but not the stem, because it feels like an ascender like in your
"flat" example
Thanks Jean,
L
On Fri, Nov 17,
Le vendredi 17 novembre 2023 à 11:44 +0100, Luca Fascione a écrit :
> Nice. Thanks Jean. This solves it for my current score
>
> In general, what's the background for this not working though?
> You seem to imply it's intended behaviour that it would only work on a single
> event, or am I misreadin
Nice. Thanks Jean. This solves it for my current score
In general, what's the background for this not working though?
You seem to imply it's intended behaviour that it would only work on a
single event, or am I misreading?
Also, can't lilypond support a mechanism like TeX's \left \right system to
Le vendredi 17 novembre 2023 à 10:58 +0100, Luca Fascione a écrit :
> Hi all,
> I noticed that in \chordmode the \parenthesize command only seems to word with
> one chord
>
> If I use
>
> \new ChordNames { \chordmode { \parenthesize a:m7 } }
>
> I get a chord in parentheses.
> If I use
>
> \new
Hi all,
I noticed that in \chordmode the \parenthesize command only seems to word
with one chord
If I use
\new ChordNames { \chordmode { \parenthesize a:m7 } }
I get a chord in parentheses.
If I use
\new ChordNames { \chordmode { \parenthesize { a:m7 d:7} } }
I do not get two chords in parent
12 matches
Mail list logo
