> 28x { d a b fs | g d g a }
I like that, thanks! Carl's concerns w.r.t. whitespace are valid,
though. Would it be possible to make the invalid syntax '28 x'
produce a nice error message like
invalid , did you mean '28x'?
Werner
On 9/28/21, 6:16 PM, "Dan Eble" wrote:
On Sep 28, 2021, at 20:12, Carl Sorensen wrote:
>
> Would
>28 x { d a b fs | g d g a }
>
> Work with the current MR?
No, the x is a suffix. 28 would be parsed as a duration (an invalid one)
and x as a note
On Sep 28, 2021, at 20:12, Carl Sorensen wrote:
>
> Would
>28 x { d a b fs | g d g a }
>
> Work with the current MR?
No, the x is a suffix. 28 would be parsed as a duration (an invalid one) and x
as a note name (an invalid one).
—
Dan
On 9/28/21, 5:51 PM, "lilypond-devel on behalf of Dan Eble"
wrote:
> 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
> 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 the difference between c1*5
>
> 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?
I mean, passing numerical values plus a dimension scaling variable
like 'mm' to
Werner LEMBERG writes:
>>> #(set-default-paper-size (cons (* 100 mm) (* 50 mm)))
>>> ```
>>>
>>> doesn't work;
>>>
>>> What must I do to make 'mm' and similar dimension scale values
>>> available at the top level?
>>
>> Why would you not use it in the paper block? mm is not a constant,
>> it
On 2021-09-28 9:21 am, Werner LEMBERG wrote:
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
>> #(set-default-paper-size (cons (* 100 mm) (* 50 mm)))
>> ```
>>
>> doesn't work;
>>
>> What must I do to make 'mm' and similar dimension scale values
>> available at the top level?
>
> Why would you not use it in the paper block? mm is not a constant,
> it depends on the output scale.
OK,
David Kastrup writes:
> Werner LEMBERG writes:
>
>> Using it with
>>
>> ```
>> #(set-default-paper-size (cons 100 50)))
>> ```
>>
>> works like a charm. However, code like
>>
>> ```
>> #(set-default-paper-size (cons (* 100 mm) (* 50 mm)))
>> ```
>>
>> doesn't work; I get the error message
>>
Werner LEMBERG writes:
> Using it with
>
> ```
> #(set-default-paper-size (cons 100 50)))
> ```
>
> works like a charm. However, code like
>
> ```
> #(set-default-paper-size (cons (* 100 mm) (* 50 mm)))
> ```
>
> doesn't work; I get the error message
>
> ```
> error: GUILE signaled an error for
Lukas-Fabian Moser writes:
>>> I answer somewhat orthogonally to your question: I think that for many
>>> people it's a lot easier to digest the information
>>>
>>> "\* creates unfolded repeats; this behaviour may be changed using
>>> \defaultRepeatType percent"
>> That is one step forward, one
Folks,
This is a comment of mine from !929:
==
The change to enable pairs [in `#(set-default-paper-size)`] is almost
trivial:
```
--- a/scm/paper.scm
+++ b/scm/paper.scm
@@ -314,7 +314,9 @@ unless explicitly overridden in
I answer somewhat orthogonally to your question: I think that for many
people it's a lot easier to digest the information
"\* creates unfolded repeats; this behaviour may be changed using
\defaultRepeatType percent"
That is one step forward, one step back: one advantage of a fixed
shorthand
Lukas-Fabian Moser writes:
> I answer somewhat orthogonally to your question: I think that for many
> people it's a lot easier to digest the information
>
> "\* creates unfolded repeats; this behaviour may be changed using
> \defaultRepeatType percent"
That is one step forward, one step back:
Hello,
Here is the current patch countdown list. The next countdown will be on
September 30th.
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
!925 Doc-de: Remove incorrect figured bass issue - Michael
Maybe it helps to give some context: The discussion started with the
problem of skipping notes in lyrics (using \addlyrics {} / \lyricsto
{}) in the documentation. In order to skip multiple notes, the
documentation currently suggests ugly things like
\repeat unfold 2 { \skip 1 }
that
a)
Jean Abou Samra writes:
> This seems a likely cause for current success:
>
>
> commit b0c6d48388c66aa12a472a6069f5b2ec07c579b2
> Author: Han-Wen Nienhuys
> Date: Sun Feb 14 11:15:17 2021 +0100
>
> Initialize session from a dedicated parser
>
> The session mechanism reads the
Le 27/09/2021 à 23:52, David Kastrup a écrit :
Jean Abou Samra writes:
is not entirely true: once a function is defined, it can be
relied on internally. Imagine my embarrassment when I had to
explain on -user-fr the cause of the error occurring with
the code (minimized here):
cons = \markup
19 matches
Mail list logo
