Again, I can confirm the crash with version 2.10.33 in Linux.
Version 2.11 works well also with this example.
Time to upgrade?
/Mats
Marcus Macauley wrote:
This one is weird. Apparently some combinations of polyphony, manual
beams, and a dotted rest followed by a note, trigger a Wrong type
Date: Fri, 28 Mar 2008 01:20:41 -0300
From: Han-Wen Nienhuys [EMAIL PROTECTED]
Subject: Re: no compile on version 2.11.43 for Windows XP
To: Tom Richard [EMAIL PROTECTED]
Cc: bug-lilypond@gnu.org
Message-ID:
[EMAIL PROTECTED]
Content-Type: text/plain; charset=UTF-8
Can you try 2.11.43-2
When using cross staff arpeggios a collision can occur if accidentals
cause the arpeggio to be moved to the left too much.
(Possible related issue: 556)
Thanks!
-Jay
\version 2.11.42
\paper
{
ragged-right = ##t
}
\book
{
\new PianoStaff
\set PianoStaff.connectArpeggios = ##t
I would expect \f to look similar to other dynamic markings like \p or
\mf when using vim. Adding it to the
.../usr/share/lilypond/current/vim/syntax/lilypond-words.vim will fix
this. Thanks!
-Jay
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Hi Jay,
I've noticed this happening recently. As a workaround I've been
setting #'infinite-spacing-height = ##t whenever it occurs.
Here's a related example with one stave and two voices where the
arpeggio collides with the time signature:
\version 2.11.42
\paper { ragged-right = ##t }
\new
Great! Thanks that worked wonderfully. Thanks!
On Fri, Mar 28, 2008 at 2:41 PM, Neil Puttock [EMAIL PROTECTED] wrote:
Hi Jay,
I've noticed this happening recently. As a workaround I've been
setting #'infinite-spacing-height = ##t whenever it occurs.
Here's a related example with one
