[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-bug
Subject:    Re: Collision between note beams and chords using tabFullNotation
From:       Keith OHara <k-ohara5a5a () oco ! net>
Date:       2012-07-22 17:08:44
Message-ID: loom.20120722T185612-567 () post ! gmane ! org
[Download RAW message or body]

Mark Brophy <mark <at> brophyworld.com> writes:

> % This bug is a "tiny example" because nothing can be removed; the bug 
> % is a consequence of a dense set of eighth and sixteenth notes placed 
> % in guitar tablature using tabFullNotation.

Thanks.  Tiny enough to unambiguously show the problem is good.
(You might be surprised how easy it is to completely miss the point of a bug
report, if the example does too many things.)

I put in a forced line-break, so minor layout changes don't hide the bug, 
and entered it in the bug tracker.
 http://code.google.com/p/lilypond/issues/detail?id=2691

Workaround:
  \once\override ChordNames.ChordName #'minimum-Y-extent = #'(-2 . 0)
at the measure with the worst collision.



[prev in list] [next in list] [prev in thread] [next in thread]