Updates:
Labels: -Patch-needs_work
Comment #11 on issue 400 by julien.r...@gmail.com: collision clef and beam
http://code.google.com/p/lilypond/issues/detail?id=400
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-l
Updates:
Status: Verified
Comment #10 on issue 400 by colinpkc...@gmail.com: collision clef and beam
http://code.google.com/p/lilypond/issues/detail?id=400
Verified with 2.13.57
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.
Updates:
Status: Fixed
Comment #9 on issue 400 by mts...@gmail.com: collision clef and beam
http://code.google.com/p/lilypond/issues/detail?id=400
Removed with the beam collision engraver (version 2.13.57).
Attachments:
foo.png 1.1 KB
_
Comment #8 on issue 400 by mts...@gmail.com: collision clef and beam
http://code.google.com/p/lilypond/issues/detail?id=400
Sorry - spoke too soon.
The workaround is:
\relative {
c8 [ \clef bass a, ] c,4
}
The beam collision engraver cannot account for automatic beams (yet).
___
Comment #7 on issue 400 by mts...@gmail.com: collision clef and beam
http://code.google.com/p/lilypond/issues/detail?id=400
Beam collisions as currently implemented do not deal with this sort of
collision automatically. I'm not sure why, as clefs are accounted for in
the beam collision engr
Comment #6 on issue 400 by colinpkc...@gmail.com: collision clef and beam
http://code.google.com/p/lilypond/issues/detail?id=400
Graham/Mike: given Graham's reg test and Mike's comment, should this issue
be marked Fixed or perhaps Patch-Review?
__
Comment #5 on issue 400 by mts...@gmail.com: collision clef and beam
http://code.google.com/p/lilypond/issues/detail?id=400
My most recent patch for Issue 37 fixes this issue.
http://codereview.appspot.com/4022045
___
bug-lilypond mailing list
bug-li
Updates:
Labels: -Patch Patch-needs_work
Comment #4 on issue 400 by percival.music.ca: collision clef and beam
http://code.google.com/p/lilypond/issues/detail?id=400
Mike, was your patch on Jan 10 a serious one? I'm not certain where we
stand on this particular issue... I suspect that
Updates:
Labels: Patch
Comment #3 on issue 400 by neziap: collision clef and beam
http://code.google.com/p/lilypond/issues/detail?id=400
http://lists.gnu.org/archive/html/lilypond-devel/2011-01/msg00301.html
___
bug-lilypond mailing list
bug-
Updates:
Owner: ---
Labels: -Priority-Medium Priority-High
Comment #2 on issue 400 by percival.music.ca: collision clef and beam
http://code.google.com/p/lilypond/issues/detail?id=400
Historically, all collisions were low.
Attachments:
foo.preview.png 1.7 KB
--
You rec
2008/10/26 Graham Percival <[EMAIL PROTECTED]>:
> Because it's a collision, and clef changes in the middle of beams
> are relatively rare.
Not to me. (And I'm not speaking as a pianist, since this is precisely
a cello part that made me realize that :-)
Cheers,
Valentin
On Sun, Oct 26, 2008 at 02:56:16AM -0700, [EMAIL PROTECTED] wrote:
> Issue 400: collision clef and beam
> http://code.google.com/p/lilypond/issues/detail?id=400
>
> Comment #1 by v.villenave:
> Why "low"?
Because it's a collision, and clef changes in the middle of beams
are relatively rare.
And d
Issue 400: collision clef and beam
http://code.google.com/p/lilypond/issues/detail?id=400
Comment #1 by v.villenave:
Why "low"?
Issue attribute updates:
Labels: -Priority-Low Priority-Medium
--
You received this message because you are listed in the owner
or CC fields of this issue, or
Issue 400: collision clef and beam
http://code.google.com/p/lilypond/issues/detail?id=400
New issue report by gpermus:
\version "2.11.28"
\relative {
c8 \clef bass a, c,4
}
Attachments:
foo.preview.png 2.2 KB
Issue attributes:
Status: Accepted
Owner: gpermus
14 matches
Mail list logo
