Re: Another arpeggio collision

2008-04-04 Thread Valentin Villenave
Hi Jay, hi Neil, All of this conversation has been added as http://code.google.com/p/lilypond/issues/detail?id=601 I've been myself experiencing similar problems with cross-staff arpeggios, because I use the following trick in my piano parts: I remove the "Time_signature_engraver" from the Staff

Issue 601 in lilypond: Accidentals cause cross-staff or cross-voice arpeggio collisions

2008-04-04 Thread codesite-noreply
Issue 601: Accidentals cause cross-staff or cross-voice arpeggio collisions http://code.google.com/p/lilypond/issues/detail?id=601 Comment #2 by v.villenave: A possible workaround is to set #'infinite-spacing-height = ##t whenever it occurs. Here's a related example with one stave and two voic

Re: manual for version 2.10.33

2008-04-04 Thread Graham Percival
On Fri, 4 Apr 2008 15:58:16 + (UTC) David <[EMAIL PROTECTED]> wrote: > I've printed out all of the user manual for LilyPond version 2.10.33, I hope that you realize that the manual for 2.10.33 is almost a year old, and the docs have undergone massive improvements in 2.11. > except that every

manual for version 2.10.33

2008-04-04 Thread David
I've printed out all of the user manual for LilyPond version 2.10.33, except that every attempt to print page 2 (which must be specified as page 11 on the 'Print' window) results only in the printing of the following (which I don't understand): ERROR NAME; ioerror COMMAND; fill OPERA