Re: octave-check doesn't work with commas for octave specification
Many thanks to both of your great bug report!
http://code.google.com/p/lilypond/issues/detail?id=201
Cheers,
- Graham
Carl Sorensen wrote:
I'm not top posting
% If octave-check is used with commas (for octaves below middle c), it assigns
the % octave as if they were quotes (for octaves above middle c)
\version 2.10.0 %Windows XP
\paper {ragged-right = ##t}
\relative c' { g g' g=,, g,,}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: merge-differently-headed works only with the first two voices in a {} \ {} \ {} construct
Thanks for the bug report! I've added it as:
http://code.google.com/p/lilypond/issues/detail?id=202
Two small nitpicks: since the \override command affects the Staff, you
only need one of them. In addition, it's easier to see what's happening
when the music is spaced vertically, rather than fitting many things
onto each line.
Thanks again,
- Graham
Carl Sorensen wrote:
% merge-differently-headed only works on the first two voices in a {} \\ {}
\\ {} construct
\paper {ragged-right = ##t}
\relative c' {
{\override Staff.NoteCollision #'merge-differently-headed = ##t d=''2 a2 } \\
{d=''8 c8 r4 a8 f'8 r4 } \\ {e,,2 e2}
{\override Staff.NoteCollision #'merge-differently-headed = ##t d=''2 a2 } \\
{e,2 e2 } \\ {d=''8 c8 r4 a8 f'8 r4 }
{ \override Staff.NoteCollision #'merge-differently-headed = ##t e,,2 e2} \\
{ d=''2 a2 } \\ {d=''8 c8 r4 a8 f'8 r4 }
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Merge-differently-headed can't accommodate three voices
% merge-differently-headed can only handle two voices
% the first shared note, d''2 and d''8 is shared between voice1 and
voice2
% the second shared note, e,8 and e'2, is shared between voice2 and
voice3
% an error message is given, and the notehead is _not_ a half note
\version 2.10.5 %Windows XP
\paper {indent = 0\mm ragged-right = ##t}
\relative c' { \override Staff.NoteCollision #'merge-differently-headed
= ##t
{d=''2 g2 } \\ {d=''8 c8 r4 \stemUp e,8 c'8 r4 } \\ { \stemDown e,,2
e'2}
}
% end of .ly snippet.
The log file information is:
Preprocessing graphical objects...
C:/Documents and Settings/Carl/My Documents/Lilypond
Source/merge-differently-headed.ly:9:11: warning: ignoring too many
clashing note columns
{d=''2
g2 } \\ {d=''8 c8 r4 \stemUp e,8 c'8 r4 } \\ { \stemDown e,,2
e'2}
Layout output to `merge-differently-headed.ps'...
Converting to `merge-differently-headed.pdf'...
Carl Sorensen
[EMAIL PROTECTED]
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Merge-differently-headed can't accommodate three voices
Carl D. Sorensen wrote: % merge-differently-headed can only handle two voices % the first shared note, d''2 and d''8 is shared between voice1 and voice2 % the second shared note, e,8 and e'2, is shared between voice2 and voice3 % an error message is given, and the notehead is _not_ a half not Sorry, you were too fast for me -- Han-Wen reported that merge-differently-headed was only meant for opposing stem dirs (ie. Voice 1 2). Merging would create incorrect notation here. I'm updating the docs accordingly. - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Google issues 204, 205, 206 duplicate - please collapse
Hi Graham, Could you collapse Google issue numbers 204, 205, 206 into a single ID? I tried attaching a file (12k .png) and Google twice timed out, gave a server error, and said try again. So I did. But in fact each click of the submit button duplicated the issue (still without the attachment). Is there some rule about non-project members not being able to attach files? -- Trevor Bača [EMAIL PROTECTED] ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Google issues 204, 205, 206 duplicate - please collapse
Trevor Bača wrote: Could you collapse Google issue numbers 204, 205, 206 into a single ID? I marked 205 and 206 as duplicates. I tried attaching a file (12k .png) and Google twice timed out, gave a server error, and said try again. So I did. But in fact each click of the submit button duplicated the issue (still without the attachment). Google code is shockingly bandwidth-poor and/or poorly programmed. I've had this problem numerous times; it might help if you file an initial report, then add each attachment individually as extra information. I'm particularly annoyed that the server error page (I've seen it many times, believe me!) claims that your action wasn't successful when apparently it was. Just look at all the duplicate bug reports I've made. :| The issues to verify bug-viewing option currently includes all verified issues; that's exactly the opposite of what it's supposed to do. I filed a bug on dec 23, but I suppose I can't blame them for taking a vacation this week. Is there some rule about non-project members not being able to attach files? Not that I'm aware of. - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
