Joe Neeman gmail.com> writes:
> This is because the page breaking algorithm tries to ensure that adjacent
> pages have similar vertical spacing (removing this code gives the results
> you expected). I'll see what happens if I just remove this behaviour (the
> line breaker does it, but the old pag
On 11/4/06, Arvid Grøtting <[EMAIL PROTECTED]> wrote:
Joe Neeman gmail.com> writes:
> This is because the page breaking algorithm tries to ensure that
adjacent
> pages have similar vertical spacing (removing this code gives the
results
> you expected). I'll see what happens if I just remove th
Joe Neeman gmail.com> writes:
> > What will happen if you keep the current behaviour of the
> > line-breaker, but apply it to each section after splitting on forced
> > page breaks instead of to the whole \book? (My guess is we'll get the
> > expected behaviour, quite possibly with a speedup as
Graham Percival gmail.com> writes:
>
> Luc wrote:
> > rests under/over beams do not work correctly with \voicexxx
> >
> > \version "2.9.28" % on windows XP
> >
> > \layout {ragged-right = ##t}
> >
> > { \voiceTwo r4 r16 r a'8[ r16 d''] }
>
> Sorry, what's the problem? The rest is moved up t
> gmane wrote:
> You seem to be top-posting. Don't do that.
> so I added this text to convince it that I wasn't. Annoying, isn't it?
> The real message starts below.
When a figured bass line has durations which overlap with rests on the same
staff, it works, but it outputs a false warning:
bug
