Re: Cues recursion

[Benjamin Strecker]

David, Matteo,

On Sun, Jun 19, 2016 at 9:53 PM, David Wright <address@hidden> wrote:
> On Mon 20 Jun 2016 at 00:40:08 (+0200), address@hidden wrote:
>> I’m preparing parts for a quite complex score, and I’m using the ‘’\add 
>> quote” command for cues.
>
> Why aren't you using cues rather than quotes?
>
>> Everything is fine until I have to quote a part that contains a cue of the 
>> same one.
>> For example, cues for the first violin are extracted from the second violin 
>> that in turn has cues of the first.
>>
>> Lilypond enters in a sort of freezing and then return a 'malloc error’.
>>
>> That makes sense to me: I figure out that it recalls an endless recursion.
>> I tried to use \killCues (\addQuote “FirstViolinCue" { \killCues 
>> \FirstViolin}) bur it doesn’t work.
>
> killCues kills cues, not quotes.
>
> Cues are notes written in a part that aren't played by that part.
> Quotes are notes written in a part that are played by that part.
> So killing quotes would leave a part incomplete.
> Killing cues leaves just the notes which actually belong to the part.
>
> Cheers,
> David.
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user

Matteo is correct to be using addQuote to use the cueDuring function
(http://lilypond.org/doc/v2.19/Documentation/notation/writing-parts#formatting-cue-notes).
The problem here is not with recursive cues but recursive includes.
As things stand, you are alternately \include-ing each of the violin
parts until you run out of space.  I would recommend reorganizing your
files a little bit so you don't have to \include each of the part
files into the other.  Since you're creating both scores in the same
file (in this example), you could use \addQuote in the score file.

I'm a bit pressed for time, but I hope that helps!
Ben