Re: Breve rest collides with notes in other voices.

Whoops - obviously you can take out the first "collide" there. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Breve rest collides with notes in other voices.

In 4/2 time, full-measure breve rests in the second voice on a staff collide can collide with notes in the first voice in the bottom space on the staff. This LilyPond file demonstrates three examples; the third, which uses a rhythm from an actual piece I was typesetting, is the worst. \version "2

Re: strange spacing behavior - possible bug

Sorry for delay; it's here: http://code.google.com/p/lilypond/issues/detail?id=3418 2013/6/20 Janek Warchoł : > i'll report it. > > 2013/6/20 Karol Majewski : >> Hi, >> >> It seems to me that the strange spacing behavior, which I described here: >> >> http://lilypond.1069038.n5.nabble.com/strange-

Omitted rests should not collide with anything

If rests are omitted, they should not collide with anything. But they do. Example: \version "2.17.20" \score { << \new Staff << \new Voice { r4 } \new Voice { \omit Rest r4 } >> >> } I get a warning: rests.ly:6:20: warning: cannot resolve rest collision: rest dir

articulate.ly generates incorrect tempo

articulate.ly can generate wrong tempo if \tempo is not set explicitly in the beginning of every voice. Let's see this example: \version "2.16.0" \include "articulate.ly" \score { \articulate << \new Voice { c4 c4-"rit." } >> \midi { \tempo 4=200 } } From the midi2ly output: \tem

Re: Patch:Doc-enhancement identifiers

Am 21.06.2013 12:35, schrieb David Kastrup: Urs Liska writes: Do I understand correctly that using git-cl doesn't require push access to the git repository? Yes. Good That's a way to get patches in the code base without asking for push access? It is a way to get patches into _review_ wit

Re: Patch:Doc-enhancement identifiers

Urs Liska writes: > Do I understand correctly that using git-cl doesn't require push > access to the git repository? Yes. > That's a way to get patches in the code base without asking for push > access? It is a way to get patches into _review_ without asking for push access. If the patch makes

Re: Patch:Doc-enhancement identifiers

Am 21.06.2013 12:24, schrieb James: Urs, On 21 June 2013 09:40, Urs Liska > wrote: Am 18.06.2013 21:23, schrieb James: On 18/06/13 19:47, Urs Liska wrote: Am 15.06.2013 10:10, schrieb Urs Liska: Hi, a

Re: Patch:Doc-enhancement identifiers

Urs, On 21 June 2013 09:40, Urs Liska wrote: > Am 18.06.2013 21:23, schrieb James: > > On 18/06/13 19:47, Urs Liska wrote: >> >>> Am 15.06.2013 10:10, schrieb Urs Liska: >>> Hi, as discussed here: http://lists.gnu.org/archive/** html/lilypond-user/2013-06/**msg00342.html

Re: Patch:Doc-enhancement identifiers

Am 18.06.2013 21:23, schrieb James: On 18/06/13 19:47, Urs Liska wrote: Am 15.06.2013 10:10, schrieb Urs Liska: Hi, as discussed here: http://lists.gnu.org/archive/html/lilypond-user/2013-06/msg00342.html The definition of identifier names in http://www.lilypond.org/doc/v2.17/Documentation/n