[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Manipulating instrument names and staff group names
From: |
Jean Abou Samra |
Subject: |
Re: Manipulating instrument names and staff group names |
Date: |
Sat, 6 Nov 2021 21:20:54 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 |
Hi,
I think that's too optimistic.
That's the gist; just some tiny corrections to make
sure Kieren knows what he will work on:
#686 certainly involves a bit of C++ programming (the command line is
evaluated in C++).
Not necessarily, options passed with -d and never
used in C++ are handled only in Scheme, in lily.scm.
#1034 seems safe, there's no actual "programming" involved, as far as
I can see.
The NR appendix is autogenerated, so you'd need to add
a new optional keyword argument to define-music-function
like #:category for markup commands, and let the script
understand that (scm/document-identifiers.scm).
Cheers,
Jean
- Re: Manipulating instrument names and staff group names, (continued)
- Re: Manipulating instrument names and staff group names, Kieren MacMillan, 2021/11/03
- Re: Manipulating instrument names and staff group names, Jean Abou Samra, 2021/11/03
- Re: Manipulating instrument names and staff group names, Lukas-Fabian Moser, 2021/11/03
- Re: Manipulating instrument names and staff group names, Jean Abou Samra, 2021/11/03
- Re: Manipulating instrument names and staff group names, Lukas-Fabian Moser, 2021/11/04
- Re: Manipulating instrument names and staff group names, Jean Abou Samra, 2021/11/04
- Re: Manipulating instrument names and staff group names, Lukas-Fabian Moser, 2021/11/05
- Re: Manipulating instrument names and staff group names, Kieren MacMillan, 2021/11/06
- Re: Manipulating instrument names and staff group names, Jean Abou Samra, 2021/11/06
- Re: Manipulating instrument names and staff group names, Lukas-Fabian Moser, 2021/11/06
- Re: Manipulating instrument names and staff group names,
Jean Abou Samra <=