I'm experiencing the collision (arpeggio & time signature) mentioned in Issue
601 (see http://code.google.com/p/lilypond/issues/detail?id=601).
The workaround recommended therein doesn't help. I use LilyPond 2.12.2,
so instead of "\override Xxx #'infinite-spacing-height = ##t"
I've tried
> I'm not top posting.
Things look much better after issuing "\override Beam #'concaveness = #0"
(or some mild value near zero - I use it \once). So the problem is gone.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/l
> I'm not top posting.
% The problem I've mentioned can easily be seen here.
% Build 2.10.33 additionally produces issue 279 stuff.
\version "2.10.0"
\new PianoStaff <<
\new Staff = RH {
\clef treble
\key des \major
\time 3/4
}
\new Staff = LH {
\clef bass
\key des \major
> I'm not top posting.
% Hi. Here is the problem I met while typesetting
% a long double-voice cross-staff running-up. I'm
% unsure if there's a shorter way to reproduce it.
% Build 2.10.33 behaves identically.
%
% Upper beam gets sloped ok, lower doesn't at all.
\version "2.11.55"
\paper { ragged
