Yes, it's documented in the Notation Reference Manual section 3.1.5 File 
Structure. It doesn't seem the obvious place to put the syntax of variable 
names.

Best regards,

Peter
mailto:[email protected]
www.ptoye.com

-------------------------

> Message: 4
> Date: Sat, 6 Mar 2021 21:30:56 +0900
> From: 田村淳 <[email protected]>
> To: "[email protected]" <[email protected]>
> Subject: Re: Workaround for (not-allowed) numbers in variable names?
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="utf-8"

> Wow! This is something I’ve been looking for for a long time. Is this 
> documented somewhere?

> Best regards,

> Jun
> https://imslp.org/wiki/User:Jun_T <https://imslp.org/wiki/User:Jun_T>

>> 2021/03/06 18:09、Richard Shann <[email protected]>のメール:

>> On Fri, 2021-03-05 at 10:15 -0800, Mogens Lemvig Hansen wrote:
>>> I believe it was David K who made this magic work:
>>>  
>>> \version "2.20.0"
>>>  
>>> mus.1 = { c d e }
>>>  
>>> \score {
>>>   \new Staff { \mus.1 }
>>> }
>>>  

>> This can be extended to cover the case where a variable has two numbers
>> associated with it:

>> 8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
>> \version "2.20.0"
>>  
>> Movement.1.Staff.1 = { c d e }
>> Movement.1.Staff.2 = { c' d' e' }
>> Movement.2.Staff.1 = { f g a } 
>> Movement.2.Staff.2 = { f' g' a' } 
>> \score {
>>   <<
>>     \new Staff { \Movement.1.Staff.1 }
>>     \new Staff { \Movement.1.Staff.2 }
>>   >>

>> }
>> \score {
>>   <<
>>   \new Staff { \Movement.2.Staff.1 }
>>     \new Staff { \Movement.2.Staff.2 }
>>   >>

>> }

>> 8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><

>> (cautionary note: I haven't examined the code or docs on this, but it
>> seems a dot before and after will do the trick mid-word and a single
>> dot at end of word)

>> A decade or so ago I resorted to converting all the numbers to Roman
>> numerals using a C routine that's knocking around on the interweb...
>> time I upgraded that.

>> Richard Shann



>>> Regards,
>>> Mogens
>>>  
>>> From: Silvain Dupertuis
>>> Sent: March 5, 2021 10:12
>>> To: [email protected]
>>> Subject: Re: Workaround for (not-allowed) numbers in variable names?
>>>  
>>> I also wondered why numbers are not allowed in variables.
>>> As for me, I used things like A, B, C instead... but it is less
>>> practical.
>>>  
>>> My guess is that it may be linked to the way numbers are used in
>>> notes and chords to indicate duration, otherwise it would be real
>>> nice to be able to use digits in variable names...!
>>>  
>>> Le 05.03.21 à 17:37, stefano franchi a écrit :
>>> Here is a question for anyone who may have been using lilypond for
>>> projects involving text and many, many, short and similar musical
>>> snippets.
>>>  
>>> I am putting together a book that will contain many (very brief) 
>>> exercises, grouped thematically. I had thought a convenient and
>>> flexible way to organize the material and keep future maintenance
>>> under control would be to create top level variables names for the
>>> main musical categories and sub-categories and then assign each score
>>> snippet to progressively numbered variable. So I would have, CategA-1 
>>> = {"code for one exercise"} , CategB-2 = "code for another
>>> exercise"}, and so on. Clean structure, easy to maintain and
>>> rearrange, etc.
>>>  
>>> Then I discovered that lilypond does not allow numbers in variable
>>> names.... :-(
>>>  
>>> I'd be willing to bet my use case is not particularly weird---there
>>> must have been other people encountering the same problem.
>>>  
>>> How have you guys managed it?
>>>  
>>> Cheers,
>>>  
>>> S.
>>>  

>>> --
>>> __________________________________________________
>>> Stefano Franchi

>>> [email protected]
>>> https://www.researchgate.net/profile/Stefano_Franchi
>>>  
>>> -- 
>>> Silvain Dupertuis
>>> Route de Lausanne 335
>>> 1293 Bellevue (Switzerland)
>>> tél. +41-(0)22-774.20.67
>>> portable +41-(0)79-604.87.52
>>> web: silvain-dupertuis.org
>>>  


> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> <https://lists.gnu.org/archive/html/lilypond-user/attachments/20210306/5ed2846d/attachment.html>

> ------------------------------

Reply via email to