Just wondering: Shouldn't \lyricsto be called \lyricsTo?
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Dear Lilyists,
Lyrics are linked to a set of notes using \lyricsto. Normally, e.g. when
linking to a Voice context, implicit melismata such as slurs, ties, and
explicit beams are automagically detected. The next syllable begins after the
melisma ends.
However: If you link lyrics to a Devnull c
Hi,
these might actually be considered two bugs but they are so intimately related
that I decided to report them together.
When manually setting a custom key signature by changing the Staff.keySignature
property as in the example below,
1) natural signs in front of the notes b and c are printed
I had been tearing my hair out for a long time trying to figure out why
my project was returning failed barline check notices at the last few
measures. When I reduced it to a minimum, I figured it out...it's a bug.
Observe the following snippet. There will probably be an error pointing
to the line
Issue 55: collision tie, accidental, and line break.
http://code.google.com/p/lilypond/issues/detail?id=55
Comment #7 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
Labels: fixed_2_11_12
--
You received this message because you are
Issue 139: tie misinterpreted as a slur
http://code.google.com/p/lilypond/issues/detail?id=139
Comment #6 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
Labels: fixed_2_11_12
--
You received this message because you are listed in th
Issue 138: single tie should use full tie-column formatting.
http://code.google.com/p/lilypond/issues/detail?id=138
Comment #2 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
Labels: fixed_2_11_12
--
You received this message because
