PATCHES - Countdown for September 26th
Hello, Here is the current patch countdown list. The next countdown will be on September 26th. A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: !923 Let Drum_note_performer heed separate articulation events - David Kastrup https://gitlab.com/lilypond/lilypond/-/merge_requests/923 !922 Correct bounds for sticky spanners - Jean Abou-Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/922 !909 Markup commands for conditionals - Jean Abou-Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/909 Countdown: !925 Doc-de: Remove incorrect figured bass issue - Michael Käppler https://gitlab.com/lilypond/lilypond/-/merge_requests/925 !924 Doc: small clarification of glissandoMap documentation - Jean Abou-Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/924 Review: !930 fix \book pagesize regression in lilypond-book - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/930 !929 lilypond-book: New options `paper-width` and `paper-height` - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/929 !927 Clean up Drul_array initialization and assignment - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/927 !926 Web: Add 2.22 docs to list of stable versions - Michael Käppler https://gitlab.com/lilypond/lilypond/-/merge_requests/926 !921 Draft: Add \lyricSkip and \lyricSkips $n. - Lukas-Fabian Moser https://gitlab.com/lilypond/lilypond/-/merge_requests/921 !897 support cairo backend in lilypond-book - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/897 New: No patches in New at this time. Waiting: !913 release: binaries with cairo - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/913 *** -- Regards James OpenPGP_0xAAC8D177A7F5A364.asc Description: OpenPGP public key
Re: Shortcut for \repeat unfold
> On 26 Sep 2021, at 10:16, Jean Abou Samra wrote:
>
> Le 26/09/2021 à 09:57, Hans Åberg a écrit :
>>> On 26 Sep 2021, at 06:49, Werner LEMBERG wrote:
>>>
>>> You might provide a MR, maybe it gets accepted. I still doubt that it
>>> would be a good idea.
>> There is a conflict in some contexts between {SYMBOL} and {COMMAND}, so may
>> not work. To get a regular COMMAND syntax, they should start with something
>> that SYMBOL does not.
>>
>> Otherwise you might replace the function YYText_utf8 with proper UTF-8
>> patterns, a variation of:
>>
>> /* UTF-8 character with valid Unicode code point. */
>> utf8char
>> [\x09\x0A\x0D\x20-\x7E]|[\xC2-\xDF][\x80-\xBF]|\xE0[\xA0-\xBF][\x80-\xBF]|[\xE1-\xEC\xEE\xEF]([\x80-\xBF]{2})|\xED[\x80-\x9F][\x80-\xBF]|\xF0[\x\90-\xBF]([\x80-\xBF]{2})|[\xF1-\xF3]([\x80-\xBF]{3})|\xF4[\x80-\x8F]([\x80-\xBF]{2})
>
> I concur with Werner.I don't think special characters like ×
> are easier to type than a backslash, and they are an annoyance if
> you don't have keyboard shortcuts at hand (like on a computer that
> is not your primary work device). They require more effort
> for beginners and memory of keyboard input methods for everyone.
> Plus, it's not clear how to make them work in lyrics mode and
> markup given that something like \lyricmode { ×8 } is already
> valid syntax and has legitimate uses.
I use text substitutions, which I have found to be fastest both to create and
use. For example, I have set ".x" to translate to "×".
Re: Shortcut for \repeat unfold
Le 26/09/2021 à 09:57, Hans Åberg a écrit :
On 26 Sep 2021, at 06:49, Werner LEMBERG wrote:
The idea here is different, it is for identifiers, and in the
input syntax only, does not change the internal semantics at all.
It is good not having to type backslash when a command is used.
Really? I highly doubt that. In particular, what about lyrics
mode?
The idea would be to change the file lexer.ll by adding U and
UCOMMAND:
A [a-zA-Z\200-\377]
U [\200-\377]
AA {A}|_
N [0-9]
ANY_CHAR(.|\n)
SYMBOL {A}([-_]{A}|{A})*
COMMAND \\{SYMBOL}
UCOMMAND{U}{SYMBOL}
Then in select places, that is context switches, add {UCOMMAND}:
{COMMAND} {
return scan_escaped_word (YYText_utf8 () + 1);
}
{UCOMMAND} {
return scan_escaped_word (YYText_utf8 ());
}
You might provide a MR, maybe it gets accepted. I still doubt that it
would be a good idea.
There is a conflict in some contexts between {SYMBOL} and {COMMAND}, so may not
work. To get a regular COMMAND syntax, they should start with something that
SYMBOL does not.
Otherwise you might replace the function YYText_utf8 with proper UTF-8
patterns, a variation of:
/* UTF-8 character with valid Unicode code point. */
utf8char
[\x09\x0A\x0D\x20-\x7E]|[\xC2-\xDF][\x80-\xBF]|\xE0[\xA0-\xBF][\x80-\xBF]|[\xE1-\xEC\xEE\xEF]([\x80-\xBF]{2})|\xED[\x80-\x9F][\x80-\xBF]|\xF0[\x\90-\xBF]([\x80-\xBF]{2})|[\xF1-\xF3]([\x80-\xBF]{3})|\xF4[\x80-\x8F]([\x80-\xBF]{2})
I concur with Werner.I don't think special characters like ×
are easier to type than a backslash, and they are an annoyance if
you don't have keyboard shortcuts at hand (like on a computer that
is not your primary work device). They require more effort
for beginners and memory of keyboard input methods for everyone.
Plus, it's not clear how to make them work in lyrics mode and
markup given that something like \lyricmode { ×8 } is already
valid syntax and has legitimate uses.
Regards,
Jean
Re: Shortcut for \repeat unfold
> On 26 Sep 2021, at 06:49, Werner LEMBERG wrote:
>
The idea here is different, it is for identifiers, and in the
input syntax only, does not change the internal semantics at all.
It is good not having to type backslash when a command is used.
>>>
>>> Really? I highly doubt that. In particular, what about lyrics
>>> mode?
>>
>> The idea would be to change the file lexer.ll by adding U and
>> UCOMMAND:
>>
>> A[a-zA-Z\200-\377]
>> U[\200-\377]
>> AA {A}|_
>> N[0-9]
>> ANY_CHAR (.|\n)
>> SYMBOL {A}([-_]{A}|{A})*
>> COMMAND \\{SYMBOL}
>> UCOMMAND {U}{SYMBOL}
>>
>> Then in select places, that is context switches, add {UCOMMAND}:
>> {COMMAND} {
>> return scan_escaped_word (YYText_utf8 () + 1);
>> }
>> {UCOMMAND} {
>> return scan_escaped_word (YYText_utf8 ());
>> }
>
> You might provide a MR, maybe it gets accepted. I still doubt that it
> would be a good idea.
There is a conflict in some contexts between {SYMBOL} and {COMMAND}, so may not
work. To get a regular COMMAND syntax, they should start with something that
SYMBOL does not.
Otherwise you might replace the function YYText_utf8 with proper UTF-8
patterns, a variation of:
/* UTF-8 character with valid Unicode code point. */
utf8char
[\x09\x0A\x0D\x20-\x7E]|[\xC2-\xDF][\x80-\xBF]|\xE0[\xA0-\xBF][\x80-\xBF]|[\xE1-\xEC\xEE\xEF]([\x80-\xBF]{2})|\xED[\x80-\x9F][\x80-\xBF]|\xF0[\x\90-\xBF]([\x80-\xBF]{2})|[\xF1-\xF3]([\x80-\xBF]{3})|\xF4[\x80-\x8F]([\x80-\xBF]{2})
