On 2020-08-29 10:38 am, David Kastrup wrote:
Aaron Hill writes:
Is this pushing things too far?
Well, essentially a similar problem. How do you figure out the
difference between setting something to a context mod, and making a
smart alist modification?
I do not believe there are any contex
Aaron Hill writes:
> On 2020-08-29 6:44 am, David Kastrup wrote:
>> Hm. \with instead of = would even fit into the parser. But that
>> leaves
>> tweaks in the lurch.
>
> Not sure I am following. Are you indicating that something like...
>
>
> \once \override LaissezVibrerTie.details
>
Aloha.
There seems to be something wrong with the lilypond mailserver. I'm
getting 6 copies (or 3 depending on how you count). Is anyone else
experiencing this? It's been going on for months, I just haven't
bothered complaining.
J.
On 8/28/20 22:17, Werner LEMBERG wrote:
>> Maybe
>>
>> \void
On 2020-08-29 6:44 am, David Kastrup wrote:
Hm. \with instead of = would even fit into the parser. But that
leaves
tweaks in the lurch.
Not sure I am following. Are you indicating that something like...
\once \override LaissezVibrerTie.details
\with { ratio = #0.5 height-limit =
> \propertyTweak finger-code #'below-string
> FretBoard.fret-diagram-details
>
> is completely indistinguishable from
>
> \propertyTweak fret-diagram-details.finger-code #'below-string
> FretBoard
>
> So any commands stacked before this last \propertyTweak command have
> no way of knowing
On 2020-08-29 6:37 am, David Kastrup wrote:
Aaron Hill writes:
On 2020-08-29 5:23 am, David Kastrup wrote:
Wols Lists writes:
On 29/08/20 05:45, Werner LEMBERG wrote:
\once \override FretBoard.size = #'1.0
\once \override FretBoard.fret-diagram-details.barre-type =
#'straight
Aaron Hill writes:
> No need to rewrite anything. We can use \with to assist with this
> pattern:
>
>
> overrideII =
> #(define-music-function
> (prop mods)
> (key-list? ly:context-mod?)
> (define (assign? mod) (eq? 'assign (car mod)))
> (define (proc mod)
> (let ((subprop (cadr
Aaron Hill writes:
> On 2020-08-29 5:23 am, David Kastrup wrote:
>> Wols Lists writes:
>>
>>> On 29/08/20 05:45, Werner LEMBERG wrote:
\once \override FretBoard.size = #'1.0
\once \override FretBoard.fret-diagram-details.barre-type =
#'straight
\once \overr
Am Samstag, den 29.08.2020, 14:14 +0200 schrieb bart deruyter:
> Thanks for the update, I'll look into how I can change my document so
> it uses lyluatex only. I used lyluatex to include complete scores in
> my document, not for single musical signs, for that I used
> lilyglyphs.
That's the idea,
On 2020-08-29 5:23 am, David Kastrup wrote:
Wols Lists writes:
On 29/08/20 05:45, Werner LEMBERG wrote:
\once \override FretBoard.size = #'1.0
\once \override FretBoard.fret-diagram-details.barre-type =
#'straight
\once \override FretBoard.fret-diagram-details.dot-color =
On 2020-08-28 9:45 pm, Werner LEMBERG wrote:
No. I'm against it. Introducing abbreviations into examples is a
slippery slope and sets a bad precedent. In my scores I use \t for
\tuplet, but I would never inflict that on any public example, even
to save space. Wrapped lines are not a visual or
On 2020-08-29 3:19 am, Wols Lists wrote:
On 29/08/20 05:45, Werner LEMBERG wrote:
\once \override FretBoard.size = #'1.0
\once \override FretBoard.fret-diagram-details.barre-type =
#'straight
\once \override FretBoard.fret-diagram-details.dot-color =
#'black
\once \over
Wols Lists writes:
> On 29/08/20 05:45, Werner LEMBERG wrote:
>> \once \override FretBoard.size = #'1.0
>> \once \override FretBoard.fret-diagram-details.barre-type = #'straight
>> \once \override FretBoard.fret-diagram-details.dot-color = #'black
>> \once \override FretBo
Thanks for the update, I'll look into how I can change my document so it
uses lyluatex only. I used lyluatex to include complete scores in my
document, not for single musical signs, for that I used lilyglyphs.
Actually I'm considering to drop the latex road and switch to libreoffice,
for one big im
Werner LEMBERG writes:
>>> BTW, would it be possible to enhance `\propertyTweak` to write
>>>
>>> \propertyTweak fret-diagram-details.dot-color #'white
>>> FretBoard
>>>
>>> as
>>>
>>> \propertyTweak dot-color #'white
>>> FretBoard.fret-diagram-details
>> BTW, would it be possible to enhance `\propertyTweak` to write
>>
>> \propertyTweak fret-diagram-details.dot-color #'white
>> FretBoard
>>
>> as
>>
>> \propertyTweak dot-color #'white
>> FretBoard.fret-diagram-details ?
>
> Have you even tried?
Only
On 29/08/20 05:45, Werner LEMBERG wrote:
> \once \override FretBoard.size = #'1.0
> \once \override FretBoard.fret-diagram-details.barre-type = #'straight
> \once \override FretBoard.fret-diagram-details.dot-color = #'black
> \once \override FretBoard.fret-diagram-details.fi
Werner LEMBERG writes:
>> Maybe
>>
>> \void \displayLilyMusic
>> \once
>> \propertyTweak color #red
>> \propertyTweak font-size #3
>> \propertyTweak direction #UP Voice.Slur
>>
>> helps?
>
> It does, thanks a lot! I didn't have this function on my radar, and
> it isn't documented in the NR at
18 matches
Mail list logo
