Re: include lines in breve X-extent (issue 1814) (issue 4931043)

http://codereview.appspot.com/4931043/diff/1/mf/feta-noteheads.mf File mf/feta-noteheads.mf (right): http://codereview.appspot.com/4931043/diff/1/mf/feta-noteheads.mf#newcode183 mf/feta-noteheads.mf:183: set_char_box (stemthick# * linecount + gap# * (linecount - 1), Jan, the breves seem to be th

Re: Issue 2512 in lilypond: Patch: Fix MIDI output for Kievan

://code.google.com/p/lilypond/issues/detail?id=2512 Counted down to 20120508, please push. @Alexandr: if need be, you can send me a formatted patch, and I'll push it for you. Pushed to staging as 9e52e03f6d8c4958c3c5335113332310c5c437c7 Thanks for the contribution to Lilypond, Alexandr! Colin --

PATCH: Countdown to 20120410

For 23:00 MDT Thursday, May 10: later because I'm rehearsing with EsQuire* Critical: Issue 2523 : Patch: Display postevents on drum notes, rests and spacer rests - R 6195059 Enhancement:

Re: Substitute for s1*0

Hello, On 7 May 2012 22:28, David Kastrup wrote: > Pavel Roskin writes: > >> On Sun, 06 May 2012 10:34:24 +0200 >> David Kastrup wrote: >> >>> Quick: tell me what you would expect without too much thinking >>> (imagine you are a naive user) from the following: >>> >>> \new Staff << >>>   \relat

CG: add updating of lilypond.pot in the release process (issue 6195060)

Reviewers: Graham Percival, Message: Both when releasing a stable or unstable version. Description: CG: add updating of lilypond.pot in the release process Please review this at http://codereview.appspot.com/6195060/ Affected files: M Documentation/contributor/release-work.itexi Index: Doc

Re: Substitute for s1*0

"Trevor Daniels" writes: > No. Didn't I list <> as an possibility? The goal being to find the > consensus solution. You have a firm opinion about what is best; > others disagree. No, they don't. Not a single reasoning has been countered. They just don't like it. You are looking for a compr

Re: Substitute for s1*0

David Kastrup wrote Tuesday, May 08, 2012 11:06 AM "Trevor Daniels" writes: Keith OHara wrote Tuesday, May 08, 2012 3:48 AM I suggest we mention that <> takes no time in NR 1.5.1 Chorded Notes, but avoid it in the examples. Most of the visible uses of s1*0 in the docs were instigated by m

Re: Substitute for s1*0

"Trevor Daniels" writes: > Keith OHara wrote Tuesday, May 08, 2012 3:48 AM > > >> Trevor Daniels treda.co.uk> writes: >> >>> Yes, I now agree. We can't continue to advocate s1*0 >>> in the docs now we are aware of these pitfalls. >> >> I suggest we mention that <> takes no time in NR 1.5.1 Chor

Re: Substitute for s1*0

Keith OHara wrote Tuesday, May 08, 2012 3:48 AM Trevor Daniels treda.co.uk> writes: Yes, I now agree. We can't continue to advocate s1*0 in the docs now we are aware of these pitfalls. I suggest we mention that <> takes no time in NR 1.5.1 Chorded Notes, but avoid it in the examples.

Re: I'd like to help and solve <> misunderstanding - if i can...

Janek Warchoł writes: > Of course i'm not in a position to instruct you; i'd just like to > share my thoughts. > > I think some of you take this discussion too personally and i'm afraid > that this can result (already resulted?) in a serious conflict :( The most hated and despised man after a sy