Re: Issue 1152 in lilypond: Regression: collisions with accidentals

2010-08-03 Thread lilypond
Updates: Labels: -fixed_2_13_29 Comment #18 on issue 1152 by percival.music.ca: Regression: collisions with accidentals http://code.google.com/p/lilypond/issues/detail?id=1152 *shrug* ok, I have no idea. I created that last image just like I used to create all the previous ones.

Re: Issue 1152 in lilypond: Regression: collisions with accidentals

2010-08-03 Thread lilypond
Comment #17 on issue 1152 by percival.music.ca: Regression: collisions with accidentals http://code.google.com/p/lilypond/issues/detail?id=1152 another test, sorry. Attachments: foo.preview.png 1.7 KB ___ bug-lilypond mailing list bug-li

Re: Issue 1152 in lilypond: Regression: collisions with accidentals

2010-08-03 Thread lilypond
Comment #16 on issue 1152 by percival.music.ca: Regression: collisions with accidentals http://code.google.com/p/lilypond/issues/detail?id=1152 WTF?! I definitely expected that one to work. ok, let's try again, with all lower-case. Attachments: foo.png 16.6 KB ___

Re: Issue 1152 in lilypond: Regression: collisions with accidentals

2010-08-03 Thread lilypond
Comment #15 on issue 1152 by percival.music.ca: Regression: collisions with accidentals http://code.google.com/p/lilypond/issues/detail?id=1152 Here's a re-uploaded image from comment 11. I suspect that google code is case-sensitive about the .PNG portion. :( Attachments: Captur

LilyPond 2.12.3 crash (Mac OS X)

2010-08-03 Thread Robert Kennedy
> I am not top-posting. Sorry I'm not able to make the source file below any shorter; it seems like if I take anything out, the bug doesn't manifest. $ /Applications/LilyPond.app/Contents/Resources/bin/lilypond bug3.ly GNU LilyPond 2.12.3 Processing `bug3.ly' Parsing... Interpreting music... [8]S

Re: ligature bracket engraver

2010-08-03 Thread Neil Puttock
On 3 August 2010 13:43, PálBenkő wrote: > I'm happy to work on this, but I need guidance. Try this: \override LigatureBracket #'bracket-visibility = ##t It would make sense (at least until somebody decides to rewrite the ligature bracket code so it doesn't rely on tuplet brackets; see issue #8

Re: Possible bug in 2.12.[23]

2010-08-03 Thread James
hello On 03/08/2010 17:03, Herman Grootaers wrote: So I started to upgrade a number of scores I had already done and I discovered the following excerpt which does behave weird. It is in the alto-part of a four-voice a-capella choir-piece which in one bar is split. The lyrics however are not hand

Re: Possible bug in 2.12.[23]

2010-08-03 Thread Phil Holmes
This would appear to be a feature of the "implicit" voice creation, as described in the Notation Reference 1.5.2. If you explicitly name the voices: alt = \relative c'' { a2 << { \voiceTwo \stemDown \hs \ignore e2 } \new Voice { \voiceTwo a4( gis) } >> } I think you'll find you get what you

Possible bug in 2.12.[23]

2010-08-03 Thread Herman Grootaers
> I'm not top posting. Greetings all, I have recently restarted a project of myself, because I do have some free time to spare. So I started to upgrade a number of scores I had already done and I discovered the following excerpt which does behave weird. It is in the alto-part of a four-voice

ligature bracket engraver

2010-08-03 Thread PálBenkő
hi list, ligature bracket engraver creates a spanner, but there's a slight difference from other spanners: a ligature bracket should end *after* the last note, even if it's the first note after a line break. I'm happy to work on this, but I need guidance. p -