Please remove this bug report again, the simple explanation is that
beams aren't
broken by default. Setting
\override Beam #'breakable = ##t
provides the desired line breaks.
This was already documented in the section on beams, but I have added the
information also in the section on line
Issue 416: removing Forbid_line_break_engraver doesn't always work
http://code.google.com/p/lilypond/issues/detail?id=416
Comment #1 by gpermus:
Never mind; beams aren't breakable by default.
Issue attribute updates:
Status: Invalid
--
You received this message because you are listed
Issue 418: tie cautionary accidental doesn't properly override following
accidental
http://code.google.com/p/lilypond/issues/detail?id=418
New issue report by lemzwerg:
\version 2.11.30
\header { texidoc =
Cautionary accidentals needed in combination with
dashed (or dotted) ties are valid
Issue 419: 2.11.30: ... (ly:font-load aybabtu): font.scm:175:29: #unknown
port:138:24: missing close paren
http://code.google.com/p/lilypond/issues/detail?id=419
New issue report by trevorbaca:
2.11.30 generates the following fatal error:
GNU LilyPond 2.11.30
Processing `0174.ly'
Parsing...
2.11.30 generates the following fatal error (entered as Google #419):
GNU LilyPond 2.11.30
Processing `0174.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing
Issue 419: 2.11.30: ... (ly:font-load aybabtu): font.scm:175:29: #unknown
port:138:24: missing close paren
http://code.google.com/p/lilypond/issues/detail?id=419
Comment #1 by trevorbaca:
It's drawing braces (GrandStaff, PianoStaff, etc) that causes the problem.
Minimal
example:
%%% BEGIN
On 8/21/07, Trevor Bača [EMAIL PROTECTED] wrote:
2.11.30 generates the following fatal error (entered as Google #419):
GNU LilyPond 2.11.30
Processing `0174.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1
