Issue 414 in lilypond: Hairpin through piano staff change cases explosions
Issue 414: Hairpin through piano staff change cases explosions http://code.google.com/p/lilypond/issues/detail?id=414 New issue report by trevorbaca: The following snippet explodes because of the hairpin at line 7: %%% EX 1 %%% \version 2.11.28 \new PianoStaff \new Staff = pianoone { \time 3/4 c'''16 \mp \ c'''16 c'''16 r16 \change Staff = pianotwo c16 c16 c16 r16 \change Staff = pianoone c'''16 c'''16 c'''16 \mf r16 } \new Staff = pianotwo { \clef bass \time 3/4 s2. } %%% END EX 1 %%% GNU LilyPond 2.11.28 Processing `0165.ly' Parsing... Interpreting music... Preprocessing graphical objects...ERROR: In procedure ly:hara-kiri-group-spanner::pure-height: ERROR: Wrong type argument in position 2: 0 rm: 0165.ps: No such file or directory Commenting out the hairpin \ at line 7 produces the otherwise correct output attached here. Attachments: hairpin-explosions.png 10.0 KB Issue attributes: Status: New Owner: Labels: Type-Defect Priority-Medium -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Hairpin through piano staff change causes explosions
Hi, Entered as Google #141, the following snippet explodes because of the hairpin at line 7: %%% EX 1 %%% \version 2.11.28 \new PianoStaff \new Staff = pianoone { \time 3/4 c'''16 \mp \ c'''16 c'''16 r16 \change Staff = pianotwo c16 c16 c16 r16 \change Staff = pianoone c'''16 c'''16 c'''16 \mf r16 } \new Staff = pianotwo { \clef bass \time 3/4 s2. } %%% END EX 1 %%% GNU LilyPond 2.11.28 Processing `0165.ly' Parsing... Interpreting music... Preprocessing graphical objects...ERROR: In procedure ly:hara-kiri-group-spanner::pure-height: ERROR: Wrong type argument in position 2: 0 rm: 0165.ps: No such file or directory Commenting out the hairpin \ at line 7 produces the otherwise correct output attached here. -- Trevor Bača [EMAIL PROTECTED] attachment: hairpin-explosions.png___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 414 in lilypond: Hairpin through piano staff change cases explosions
Issue 414: Hairpin through piano staff change cases explosions http://code.google.com/p/lilypond/issues/detail?id=414 Comment #1 by trevorbaca: ACK! Fixed in .29; please close. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Hairpin through piano staff change causes explosions
On 8/18/07, Trevor Bača [EMAIL PROTECTED] wrote: Hi, Entered as Google #141, the following snippet explodes because of the hairpin at line 7: %%% EX 1 %%% \version 2.11.28 \new PianoStaff \new Staff = pianoone { \time 3/4 c'''16 \mp \ c'''16 c'''16 r16 \change Staff = pianotwo c16 c16 c16 r16 \change Staff = pianoone c'''16 c'''16 c'''16 \mf r16 } \new Staff = pianotwo { \clef bass \time 3/4 s2. } %%% END EX 1 %%% GNU LilyPond 2.11.28 Processing `0165.ly' Parsing... Interpreting music... Preprocessing graphical objects...ERROR: In procedure ly:hara-kiri-group-spanner::pure-height: ERROR: Wrong type argument in position 2: 0 rm: 0165.ps: No such file or directory Commenting out the hairpin \ at line 7 produces the otherwise correct output attached here. ACK; I reported against .28. Fixed in .29, as the attached png shows. Please disregard and close Google #414. -- Trevor Bača [EMAIL PROTECTED] attachment: hairpin-correct.png___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 415 in lilypond: Hidden accidental of tied note still takes space
Issue 415: Hidden accidental of tied note still takes space http://code.google.com/p/lilypond/issues/detail?id=415 New issue report by wbsoft: %{ A hidden accidental of a tied note still takes space, as visible in attached PNG, measure 2. As if the accidental is transparent instead of absent. %} \version 2.11.29 % or git as of August 18, 2007 \paper { ragged-right = ##t } \new Staff \relative c'' { c2 cis~ | cis c~ | c r } \\ { c,8 d e d c d e d | c d e d c d e d | c8 d e d r2 } Attachments: hidden-acc-takes-space.png 5.5 KB Issue attributes: Status: New Owner: Labels: Type-Defect Priority-Medium -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 414 in lilypond: Hairpin through piano staff change cases explosions
Issue 414: Hairpin through piano staff change cases explosions http://code.google.com/p/lilypond/issues/detail?id=414 Comment #2 by joeneeman: (No comment was entered for this change.) Issue attribute updates: Status: Invalid -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Hidden accidental of tied note still takes space in 2.11.19
On Friday 17 August 2007 19:28, Wilbert Berendsen wrote: %{ A hidden accidental of a tied note still takes space, as visible in attached PNG, measure 2. As if the accidental is transparent instead of absent. %} Thanks, fixed. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 392 in lilypond: Wrong vim compiler file.
Issue 392: Wrong vim compiler file. http://code.google.com/p/lilypond/issues/detail?id=392 Comment #1 by joeneeman: Thanks, fixed. Issue attribute updates: Status: Fixed Labels: fixed_2_11_30 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Todays git shows #399 again I think
On Friday 17 August 2007 17:04, Wilbert Berendsen wrote: Hi, I compiled todays git (git checkout origin/master; git pull) but it looks like bug 399 has been introduced again: clefs use too much space when switching staff. http://code.google.com/p/lilypond/issues/detail?id=399 Thanks, this is fixed again. Joe ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 369 in lilypond: \change Staff=foo affects beam too early
Issue 369: \change Staff=foo affects beam too early http://code.google.com/p/lilypond/issues/detail?id=369 Comment #2 by joeneeman: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_30 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond