Aaron Hill writes:
> On 2022-05-24 7:40 am, Jean Abou Samra wrote:
>> Because there is now a command called \section, so this
>> is trying to set a key inside a music function, which is
>> not an alist ... This is unfortunate but unavoidable.
>
> Would it be practical for LilyPond to detect and w
Le 24/05/2022 à 18:06, Aaron Hill a écrit :
On 2022-05-24 7:40 am, Jean Abou Samra wrote:
Because there is now a command called \section, so this
is trying to set a key inside a music function, which is
not an alist ... This is unfortunate but unavoidable.
Would it be practical for LilyPond to
On 2022-05-24 7:40 am, Jean Abou Samra wrote:
Because there is now a command called \section, so this
is trying to set a key inside a music function, which is
not an alist ... This is unfortunate but unavoidable.
Would it be practical for LilyPond to detect and warn when a built-in is
being re
Le 24/05/2022 à 16:40, Jean Abou Samra a écrit :
this
is trying to set a key inside a music function
I have to correct myself. \section is defined as a music identifier, not
a music function.
The result is the same though.
___
bug-lilypond ma
Le 24/05/2022 à 16:37, Trevor Bača a écrit :
Hi,
The dot-chained variable names that became available in recent versions of
LilyPond are great, particularly because they allow numerals:
%%% EXAMPLE 1 %%%
\version "2.23.8"
movement.1.notes = { g'4 }
\new Staff { \movement.1.notes }
%%% END %
Hi,
The dot-chained variable names that became available in recent versions of
LilyPond are great, particularly because they allow numerals:
%%% EXAMPLE 1 %%%
\version "2.23.8"
movement.1.notes = { g'4 }
\new Staff { \movement.1.notes }
%%% END %%%
But LilyPond's parser errors when a variable