> On Sep 24, 2021, at 19:32, Jean Abou Samra wrote:
>
> - "\rep n music", not as self-telling (and I think Lukas
> only calls his shortcut \rep because redefining \repeat
> is not syntactically valid);
What about killing two birds with two stones?
1. convert-ly \times A/B into \tuplet
On 9/29/2021 6:32 PM, David Kastrup wrote:
John Wheeler writes:
On 9/29/2021 3:35 PM, David Kastrup wrote:
John Wheeler writes:
Hello,
Would someone please help me understand the reasoning behind removing
the grammar from the Contributor's Guide? Was there a licensing
issue?
It was
On 9/29/2021 6:13 PM, Jean Abou Samra wrote:
Le 30/09/2021 à 01:11, John Wheeler a écrit :
I must be the one exception to "nobody uses this", I appreciate the
"good luck" wish.
Curious: what is your use case?
I originally started down this path because I wanted to create a method
to
Forwarding to list, because I didn't reply to all. Sorry!
On 9/29/21, 8:35 PM, "Carl Sorensen" wrote:
John,
On 9/29/21, 5:12 PM, "lilypond-devel on behalf of John Wheeler"
wrote:
Thank you to both you and Jean.
I must be the one exception to
John Wheeler writes:
> On 9/29/2021 3:35 PM, David Kastrup wrote:
>> John Wheeler writes:
>>
>>> Hello,
>>>
>>> Would someone please help me understand the reasoning behind removing
>>> the grammar from the Contributor's Guide? Was there a licensing
>>> issue?
>> It was more of a matter of it
Le 30/09/2021 à 01:11, John Wheeler a écrit :
I must be the one exception to "nobody uses this", I appreciate the
"good luck" wish.
Curious: what is your use case?
On 9/29/2021 3:35 PM, David Kastrup wrote:
John Wheeler writes:
Hello,
Would someone please help me understand the reasoning behind removing
the grammar from the Contributor's Guide? Was there a licensing
issue?
It was more of a matter of it having become comparatively uninformative
due to
Jean Abou Samra writes:
> Le 30/09/2021 à 00:13, David Kastrup a écrit :
>> commit a1a418468e5cf481340667d433676dc00adf00fb
>> Author: Jean Abou Samra
>> Date: Wed Sep 1 18:54:24 2021 +0200
>>
>> Markup commands for conditionals
>>
>> has
>>
>> +@ref{Conditionals}.
>>
>> in its diff
Aaron Hill writes:
> On 2021-09-29 12:39 pm, David Kastrup wrote:
>> The question is whether we should do something like this as default,
>> possibly conditioned on whether any acknowledgers are present? Because
>> even if we cannot react to Midi data structures (since they are not
>>
Le 30/09/2021 à 00:13, David Kastrup a écrit :
commit a1a418468e5cf481340667d433676dc00adf00fb
Author: Jean Abou Samra
Date: Wed Sep 1 18:54:24 2021 +0200
Markup commands for conditionals
has
+@ref{Conditionals}.
in its diff without defining it anywhere.
It is defined in
commit a1a418468e5cf481340667d433676dc00adf00fb
Author: Jean Abou Samra
Date: Wed Sep 1 18:54:24 2021 +0200
Markup commands for conditionals
has
+@ref{Conditionals}.
in its diff without defining it anywhere. Consequently I get
dak@lola:/usr/local/tmp/lilypond$ CPU_COUNT=9 make -j9
On 2021-09-29 12:39 pm, David Kastrup wrote:
The question is whether we should do something like this as default,
possibly conditioned on whether any acknowledgers are present? Because
even if we cannot react to Midi data structures (since they are not
Scheme-accessible for now), sometimes a
Le 29/09/2021 à 17:43, John Wheeler a écrit :
Hello,
Would someone please help me understand the reasoning behind removing
the grammar from the Contributor's Guide? Was there a licensing issue?
Thank you,
John Wheeler
It was discussed at
John Wheeler writes:
> Hello,
>
> Would someone please help me understand the reasoning behind removing
> the grammar from the Contributor's Guide? Was there a licensing
> issue?
It was more of a matter of it having become comparatively uninformative
due to lots of LilyPond functionality
Hello,
Would someone please help me understand the reasoning behind removing
the grammar from the Contributor's Guide? Was there a licensing issue?
Thank you,
John Wheeler
David Kastrup writes:
> So I tried the following
>
> Stress_performer =
> #(define-scheme-function (strong weak) (index? index?)
>(lambda (ctx)
> (define fired #f)
> (define (emit weight)
>(ly:broadcast (ly:event-source ctx)
>(ly:make-stream-event
>
So I tried the following
Stress_performer =
#(define-scheme-function (strong weak) (index? index?)
(lambda (ctx)
(define fired #f)
(define (emit weight)
(ly:broadcast (ly:event-source ctx)
(ly:make-stream-event
(ly:make-event-class
Werner LEMBERG writes:
>>> OK, thanks for the pointer. But I wonder what exactly the problem
>>> is: The paper size strings passed to `set-default-paper-size` *do*
>>> contain the 'mm' variable, see `paper-alist`. Is the expansion of
>>> 'mm' delayed? Isn't there a possibility to do the same
>> OK, thanks for the pointer. But I wonder what exactly the problem
>> is: The paper size strings passed to `set-default-paper-size` *do*
>> contain the 'mm' variable, see `paper-alist`. Is the expansion of
>> 'mm' delayed? Isn't there a possibility to do the same on the top
>> level?
>
>
28x { d a b fs | g d g a }
https://gitlab.com/lilypond/lilypond/-/merge_requests/937
That is a clever proposal. I am already fond of it.
Thank you.
This looks so "natural" (in the non-computer science-way of the meaning)
one is surprised it works. :-)
What this means is that if you
Jean Abou Samra writes:
> It's not unconceivable to build whitespace into the
> lexer pattern and have { 5 x c'1 } work.
> What this means is that if you create a custom note
> name language (with the undocumented not-yet-having-interface
> #(set! language-pitch-names (acons 'mylang
>> 28x { d a b fs | g d g a }
>>
>> https://gitlab.com/lilypond/lilypond/-/merge_requests/937
>
> That is a clever proposal. I am already fond of it. Thank you.
+1
>> I like that, thanks! Carl's concerns w.r.t. whitespace are valid,
>> though. Would it be possible to make the invalid
Le 29/09/2021 à 01:50, Dan Eble a écrit :
On Sep 24, 2021, at 19:32, Jean Abou Samra wrote:
Other possibilities:
- "\rep n music", not as self-telling (and I think Lukas
only calls his shortcut \rep because redefining \repeat
is not syntactically valid);
- "music * n", attractive but
23 matches
Mail list logo
