David,
Sorry that was a typo. It should have been a hyphen.
Best regards,
Peter
mailto:lilyp...@ptoye.com
www.ptoye.com
-
Friday, November 8, 2019, 11:48:13 AM, David Kastrup wrote:
> Peter Toye writes:
>> David and others,
>> It seems that I've opened up a larger
Peter Toye writes:
> David and others,
>
> It seems that I've opened up a larger can of worms than I'd expected!
> Thanks to all for the suggestions and clarifications.
>
> From what you say Quartet_No.I_Éloge_MovementI-ViolinI is a valid
> variable name - just checking that this is correct.
David and others,
It seems that I've opened up a larger can of worms than I'd expected! Thanks to
all for the suggestions and clarifications.
From what you say Quartet_No.I_Éloge_MovementI-ViolinI is a valid variable name
- just checking that this is correct. But also (from Aaron Hill's email)
Peter Toye writes:
> Timothy,
>
> This raises a further question which I can't see answered in the
> documentation: exactly what characters are allowed in a Lilypond
> variable name? NR says that the convention is alphabetic characters
> only,
It's alphabetic characters in the ASCII set plus
On 2019-11-07 7:33 am, Peter Toye wrote:
This raises a further question which I can't see answered in the
documentation: exactly what characters are allowed in a Lilypond
variable name? NR says that the convention is alphabetic characters
only, but you seem to have found that digits and
. Is this documented, or did you experiment?
Best regards,
Peter
mailto:lilyp...@ptoye.com
www.ptoye.com
-
Monday, November 4, 2019, 6:46:05 PM, Timothy Lanfear wrote:
On 04/11/2019 09:28, Peter Toye wrote:
Re: Scoped variables
On further consideration I think that Timothy Lanfear has
On 04/11/2019 19:57, David Wright wrote:
Well, the NR §3.1.5 does say:
"A .ly file may contain any number of toplevel expressions, where a
toplevel expression is one of the following: …
• A \score block. This score will be collected with other toplevel
scores, and combined
On Mon 04 Nov 2019 at 18:46:05 (+), Timothy Lanfear wrote:
> On 04/11/2019 09:28, Peter Toye wrote:
> > Re: Scoped variables On further consideration I think that Timothy
> > Lanfear has, probably inadvertently, made my point for me.
> >
> > If a publisher want
Hmm. Interesting.
But I still prefer properly scoped variables!
Peter
-
Monday, November 4, 2019, 6:46:05 PM, Timothy Lanfear wrote:
I was surprised to find that provided there is no explicit \book statement,
variables can be redefined between bookparts and behave
On 04/11/2019 09:28, Peter Toye wrote:
Re: Scoped variables On further consideration I think that Timothy
Lanfear has, probably inadvertently, made my point for me.
If a publisher wanted to collect Mr. Lanfear's string quartets
(assuming that he has written more than one) into a single
Hi Peter,
> If a publisher wanted to collect Mr. Lanfear's string quartets (assuming that
> he has written more than one) into a single volume, the Lilypond code would
> have to be changed to rename all of the variables to something like QiIViolinI
In the engraving of my larger works (operas,
Peter,
in the article Kieren mentioned, I tried to summarize some thoughts
around the multi-movement issue and some more.
You can find the corresponding templating engine at:
https://github.com/openlilylib/lalily-templates
That framework does a lot to do things automagically. But probably this
Kieren,
That looks great at a first skim-through. Thanks.
Best regards,
Peter
mailto:lilyp...@ptoye.com
www.ptoye.com
-
Monday, November 4, 2019, 11:06:55 AM, Kieren MacMillan wrote:
> Hi Peter,
>> If a publisher wanted to collect Mr. Lanfear's string quartets
vid Kastrup wrote:
> Peter Toye writes:
>> Is there a case for introducing scoped variables into Lilypond?
>> As I understand it (please correct me if I'm wrong), variables have to be
>> declared at the top of the document, before any music expression. I'm trying
>> to wor
-
Sunday, November 3, 2019, 2:24:10 PM, David Kastrup wrote:
> Peter Toye writes:
>> Is there a case for introducing scoped variables into Lilypond?
>> As I understand it (please correct me if I'm wrong), variables have to be
>> declared at th
On 03/11/2019 12:54, Peter Toye wrote:
Scoped variables Is there a case for introducing scoped variables into
Lilypond?
As I understand it (please correct me if I'm wrong), variables have to
be declared at the top of the document, before any music expression.
I'm trying to work on a document
Peter Toye writes:
> Is there a case for introducing scoped variables into Lilypond?
>
> As I understand it (please correct me if I'm wrong), variables have to be
> declared at the top of the document, before any music expression. I'm trying
> to work on a document with many d
Is there a case for introducing scoped variables into Lilypond?
As I understand it (please correct me if I'm wrong), variables have to be
declared at the top of the document, before any music expression. I'm trying to
work on a document with many different scores, each if which is in its own
18 matches
Mail list logo
