Le dimanche 26 mars 2023 à 14:24 +0200, David Kastrup a écrit :
> Patterns like
>
> ("flageolet" .
>
> (acons "flageolet"
>
> (assoc "flageolet"
Why handle alists with articulation-type keys but not
```
(list "flageolet" ...)
(cons "flageolet" ...)
(hash-ref xxx "flageolet")
```
etc. The
Jean Abou Samra writes:
> convert-ly only does text substitutions based on patterns that are
> likely to be old syntax that needs to be converted. It cannot
> understand the logic behind Scheme code. In this snippet, it can't
> determine that what is being looked up in the alist is an
>
Le dimanche 26 mars 2023 à 07:19 -0400, Mark Mathias a écrit :
>
> On Sat, Mar 25, 2023 at 8:36 PM Jean Abou Samra
> <[j...@abou-samra.fr](mailto:j...@abou-samra.fr)> wrote:
>
> > Le samedi 25 mars 2023 à 10:58 -0400, Mark Mathias a écrit :
> >
> > > Oops... Except it doesn't. The accent
On Sat, Mar 25, 2023 at 8:36 PM Jean Abou Samra wrote:
> Le samedi 25 mars 2023 à 10:58 -0400, Mark Mathias a écrit :
>
> Oops... Except it doesn't. The accent remains black when I run it in
> 2.24.0. (I'm only beginning to get a glimmer of how to use Scheme with
> LilyPond.)
>
> In 2.24,
Le samedi 25 mars 2023 à 10:58 -0400, Mark Mathias a écrit :
> Oops... Except it doesn't. The accent remains black when I run it in 2.24.0.
> (I'm only beginning to get a glimmer of how to use Scheme with LilyPond.)
In 2.24, `articulation-type` is a symbol, not a string. You need to remove the
On 2023-03-25 7:58 am, Mark Mathias wrote:
Oops... Except it doesn't. The accent remains black when I run it in
2.24.0. (I'm only beginning to get a glimmer of how to use Scheme with
LilyPond.)
Hmm... I currently run 2.22 for my scores, and the snippet from the
email thread does appear to
> The "elegant" solution intrigues me, but the link to the thread
> appears to be down.
Yesterday and today there was a hiccup with gnu.org (and nongnu.org);
see
https://hostux.social/@fsfstatus
It seems to be fixed now.
Werner
On Sat, Mar 25, 2023 at 10:41 AM Mark Mathias wrote:
>
>
> On Sat, Mar 25, 2023, 9:21 AM Aaron Hill wrote:
>
>> On 2023-03-25 6:10 am, Mark Mathias wrote:
>> > On Fri, Mar 24, 2023, 7:59 PM Leo Correia de Verdier <
>> > leo.correia.de.verd...@gmail.com> wrote:
>> >> But if something more
On Sat, Mar 25, 2023, 9:21 AM Aaron Hill wrote:
> On 2023-03-25 6:10 am, Mark Mathias wrote:
> > On Fri, Mar 24, 2023, 7:59 PM Leo Correia de Verdier <
> > leo.correia.de.verd...@gmail.com> wrote:
> >> But if something more elegant is required (for instance if there could
> >> be
> >>
On 2023-03-25 6:10 am, Mark Mathias wrote:
On Fri, Mar 24, 2023, 7:59 PM Leo Correia de Verdier <
leo.correia.de.verd...@gmail.com> wrote:
But if something more elegant is required (for instance if there could
be
conflicting tweaks) there is a solution in this thread:
On Fri, Mar 24, 2023, 7:59 PM Leo Correia de Verdier <
leo.correia.de.verd...@gmail.com> wrote:
> The problem with that solution is that it changes all Scripts, including
> all articulations. I would suggest the somewhat hacky solution of
> redefining just the commands in case, like
>
> segno =
Leo,
I didn't spot that problem, but your \tweak snippet works perfectly.
Regards,
Laurie
Laurie Savage
https://www.queensofthewest.com/
On Sat, Mar 25 2023 at 11:16:37 +1100, Laurie Savage
wrote:
Thanks Michael,
That clarifies the problem. I'm going to see if I can incorporate the
new
Thanks Michael,
That clarifies the problem. I'm going to see if I can incorporate the
new segno-repeat structure into the score, but I suspect that might be
difficult because the Segno is at the start of a repeat and the Coda
sign is midway through a repeated passage that follows.
Laurie
Hi Leo,
On Fri, Mar 24, 2023 at 7:59 PM Leo Correia de Verdier <
leo.correia.de.verd...@gmail.com> wrote:
> The problem with that solution is that it changes all Scripts, including
> all articulations.
A very good point. That's what I get for trying to do too many things at
the same time. :)
The problem with that solution is that it changes all Scripts, including all
articulations. I would suggest the somewhat hacky solution of redefining just
the commands in case, like
segno = \tweak color #red \segno
coda = \tweak color #red \coda
But if something more elegant is required (for
Hi Laurie,
On Fri, Mar 24, 2023 at 7:19 PM savage.laurie
wrote:
> I think the issue might be that I am using explicit \coda and \segno
> commands and your example uses the new \repeat segno form which will be too
> complex in the specific big band chart I'm editing. It's about 160 bars
> long
(GMT+10:00) To: Laurie Savage
Cc: Lilypond-User Mailing List Subject: Re: Coda/Segno
sign color override not working: LiliyPond 2.24.0 Hi Laurie,On Fri, Mar 24,
2023 at 10:56 AM Laurie Savage wrote:Hi,I put this in
my layout block\context { \Score \override CodaMark.color = #red
Hi Laurie,
On Fri, Mar 24, 2023 at 10:56 AM Laurie Savage
wrote:
> Hi,
>
> I put this in my layout block
>
> \context {
> \Score
> \override CodaMark.color = #red
> \override SegnoMark.color = #red
> \override SectionLabel.color = #red
> \override
Hi,
I put this in my layout block
\context {
\Score
\override CodaMark.color = #red
\override SegnoMark.color = #red
\override SectionLabel.color = #red
\override SectionLabel.font-size = #3
\override RehearsalMark.font-size = #3
\override RehearsalMark.color
19 matches
Mail list logo
