Re: Issue 1385 in lilypond: Line indents confuse vertical spacing
Comment #3 on issue 1385 by pnorcks: Line indents confuse vertical spacing http://code.google.com/p/lilypond/issues/detail?id=1385 The virtual desktop method is good as well, I agree. Thanks for mentioning that, because I need to spend some time reconfiguring my window manager... ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1382 in lilypond: Segfault when setting 'staff-space to 0.0
Comment #5 on issue 1382 by pnorcks: Segfault when setting 'staff-space to 0.0 http://code.google.com/p/lilypond/issues/detail?id=1382 Carl: I agree. I should have time to look at this issue again this weekend. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
accidental-style surprise
% Low priority, but easy, Enhancement, or possibly Documentation % % extraNatural is quietly set to #f as part of setting the % modern-* or piano-* styles for automatic accidentals % (music-functions.scm) % This can be a confusing surprise to users not yet % familiar with what extraNatural does : { #(set-accidental-style 'piano 'Score) \key des \major 1 \bar "||" \key cis \minor 1 } % Suggest instead that choosing these styles for automatic % accidentals should set extraNatural % to the documented default of #t nontraditional.png Description: Binary data ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1382 in lilypond: Segfault when setting 'staff-space to 0.0
Comment #4 on issue 1382 by lemzwerg: Segfault when setting 'staff-space to 0.0 http://code.google.com/p/lilypond/issues/detail?id=1382 Yes, Xavier, it's the right priority. Any input to LilyPond which makes the program crash is critical. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1385 in lilypond: Line indents confuse vertical spacing
Comment #2 on issue 1385 by lemzwerg: Line indents confuse vertical spacing http://code.google.com/p/lilypond/issues/detail?id=1385 Your `alternating between them in separate tabs' is called `blink comparison' in astronomy. It's one of my favourite methods in finding smallest differences (as sometimes needed in testing rendering improvements in FreeType) since even sligthest changes pop up quite easily. On my GNU/Linux box using KDE, I've set up a bunch of virtual desktops, and I've assigned key combinations to easily switch between them; in other words, I'm not limited to a browser while doing blink comparisons, any image viewer will do. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1382 in lilypond: Segfault when setting 'staff-space to 0.0
Comment #3 on issue 1382 by Carl.D.Sorensen: Segfault when setting 'staff-space to 0.0 http://code.google.com/p/lilypond/issues/detail?id=1382 Xavier: Critical, because we ought to have error checking to prevent segfaults. Patrick: It seems like we ought to spit out a warning message and tell the user we're setting the staff-space to whatever value we are setting it to. And perhaps instead of 1, we ought to set it to 0.1 or 0.01 or something like that; if the user sets it to 0 they may really want a small value (although why, I'm not sure). ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1228 in lilypond: \override RestCollision #'positioning-done = #merge-rests-on-positioning
Comment #4 on issue 1228 by x.scheuer: \override RestCollision #'positioning-done = #merge-rests-on-positioning http://code.google.com/p/lilypond/issues/detail?id=1228 * and document it, maybe... ;P So it would be far easier for users! ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1228 in lilypond: \override RestCollision #'positioning-done = #merge-rests-on-positioning
Comment #3 on issue 1228 by x.scheuer: \override RestCollision #'positioning-done = #merge-rests-on-positioning http://code.google.com/p/lilypond/issues/detail?id=1228 Hi! This feature has been asked again by a user on the French user mailing list. Actually Wilbert's code seems to work really fine. Could a wise developer review it and then push it so it will be implemented directly into LilyPond? Many thanks to Wilbert again ! Cheers, Xavier ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1382 in lilypond: Segfault when setting 'staff-space to 0.0
Comment #2 on issue 1382 by x.scheuer: Segfault when setting 'staff-space to 0.0 http://code.google.com/p/lilypond/issues/detail?id=1382 "Priority-Critical" !? This is not a "real world" issue: who would set 'staff-space to 0.0 ?!? Cheers, Xavier ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: line indents confuse vertical spacing
On Thu, 04 Nov 2010 16:25:46 -0700, Patrick McCarty wrote: On Sun, Oct 31, 2010 at 6:17 PM, Keith E OHara wrote: I've spent a while thinking about this, and I'm not sure what to make of it. Sorry if I was too brief or unintentionally mysterious, Patrick. I certainly don't want to slow you down. I would have suggested medium priority because it has not been seen 'in the wild', and only happens in the first line of a score, but I imagine it could easily occur in real music. I agree with you in that this is a different issue than 1290, so I'll add it to the tracker (with a different example snippet). http://code.google.com/p/lilypond/issues/detail?id=1385 I can't test to see if it's a regression right now, but I assume that it is. I confirmed, using your example, that it is a regression relative to 2.12.3 -Keith ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: multiple fret-diagram-x markup commands and lilypond-book safe-mode
On Tue, Nov 2, 2010 at 3:57 PM, Julien Rioux wrote: > > I've found a strange behaviour using lilypond-book --safe on a lytex file: > With multiple snippets each containing one \fret-diagram-x markup command, > compilation works for the first snippet but fails on the next one. Then if > you run lilypond-book --safe a second time, it will successfully compile the > second snippet but fail on the third, etc. > > I attach a minimal example file and the log of the error on first run of > lilypond-book --safe. The same file compiles perfectly without the --safe > switch. I am assuming that \fret-diagram-x markup commands are allowed in > safe mode. Minimal trials with lilypond -dsafe have led me to believe that > this should work. Are you compiling LilyPond from scratch and using Guile 1.9, by chance? The reason I ask is because I have seen these errors many times with my testing of Guile 1.9 with LilyPond. If you're using Guile 1.8, I'll have a look at this again, since I can't reproduce with Guile 1.8 and latest LilyPond git. Thanks, Patrick ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1385 in lilypond: Line indents confuse vertical spacing
Comment #1 on issue 1385 by pnorcks: Line indents confuse vertical spacing http://code.google.com/p/lilypond/issues/detail?id=1385 BTW, it's easiest to see the differences in the images by alternating between them in separate tabs. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: line indents confuse vertical spacing
On Sun, Oct 31, 2010 at 6:17 PM, Keith E OHara wrote: > Dear Bug Squad, > Would you please look at the possible collision-regression in the example > below? > > It seems as if the vertical spacing engine has a different idea of what the > indents are, than does the printing engine. This matters when the indents > are different on neighboring lines, such as the first and second line of a > score. > > I should emphasize that I did *not* notice this in real music, despite my > efforts to uncover exactly this kind of problem. Instead, I found this > while looking into issue 1290, which required me to make some artificial > examples. > > I put in a non-essential tie just to give a colliding object some width, to > confirm that this is not just a near-miss kind of error. > > --8<-- > \version "2.13.38" > \score { { > \repeat unfold 16 g' > g' g' g, g' % \break > \repeat unfold 20 g' > g' g'''~g'''~g''' % the tie is not essential > } > \layout { > % indent = #2 > % short-indent = #14 > } } > % #(ly:set-option 'debug-skylines #t) I've spent a while thinking about this, and I'm not sure what to make of it. I agree with you in that this is a different issue than 1290, so I'll add it to the tracker (with a different example snippet). http://code.google.com/p/lilypond/issues/detail?id=1385 I can't test to see if it's a regression right now, but I assume that it is. Thanks, Patrick ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1385 in lilypond: Line indents confuse vertical spacing
Status: Accepted Owner: Labels: Type-Defect Priority-Critical Regression New issue 1385 by pnorcks: Line indents confuse vertical spacing http://code.google.com/p/lilypond/issues/detail?id=1385 Original report: http://lists.gnu.org/archive/html/bug-lilypond/2010-10/msg00618.html I have a created a new snippet for this report that likely demonstrates the same issue. The four images show the same snippet when `indent' is set the 1\mm, 2\mm, 3\mm, and 4\mm respectively. %%% BEGIN \version "2.13.38" #(set-default-paper-size "a6") \score { { \repeat unfold 2 { g4 g g g } g,1 \repeat unfold 2 { g4 g g g } g'''4 ~ g'''4 g'4 ~ g'4 } \layout { % Uncomment each of these in turn to see the spacing changes indent = 1 \mm % indent = 2 \mm % indent = 3 \mm % indent = 4 \mm short-indent = 1 \mm } } %%% END Attachments: spacing-1mm-indent.png 4.9 KB spacing-2mm-indent.png 4.8 KB spacing-3mm-indent.png 4.7 KB spacing-4mm-indent.png 4.6 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1384 in lilypond: annotate-spacing draws system-system instead of last-bottom
Comment #2 on issue 1384 by pnorcks: annotate-spacing draws system-system instead of last-bottom http://code.google.com/p/lilypond/issues/detail?id=1384 ... and an image showing the resulting output with this patch. Attachments: annotate-space-new.png 19.1 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: annotate-spacing draws system-system instead of last-bottom
> On Sun, Oct 24, 2010 at 10:17 PM, Patrick McCarty wrote: >> On Sun, Oct 24, 2010 at 6:46 PM, Mark Polesky wrote: >>> >>> If this is a trivial fix, it would be great if someone could >>> fix it quickly. I'm unable to understand the spacing code, >>> so I use annotate-spacing to quickly double-check my >>> understanding of the spacing docs, when I'm editing them. >> >> I don't really know the correct way of singling out the bottom system >> of each page, but the attached patch seems to work okay. Any thoughts about this, Mark? I'll add it to the tracker so it's not lost: http://code.google.com/p/lilypond/issues/detail?id=1384 -Patrick ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1384 in lilypond: annotate-spacing draws system-system instead of last-bottom
Updates: Labels: Patch Comment #1 on issue 1384 by pnorcks: annotate-spacing draws system-system instead of last-bottom http://code.google.com/p/lilypond/issues/detail?id=1384 The attached patch seems to fix the issue, though it may be an improper solution. Attachments: 0001-annotate-spacing-Add-condition-for-last-bottom-spaci.patch 846 bytes ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1384 in lilypond: annotate-spacing draws system-system instead of last-bottom
Status: Accepted Owner: Labels: Type-Defect Priority-High New issue 1384 by pnorcks: annotate-spacing draws system-system instead of last-bottom http://code.google.com/p/lilypond/issues/detail?id=1384 Reported by Mark: http://lists.gnu.org/archive/html/bug-lilypond/2010-10/msg00467.html As the attached example illustrates, the spacing for the last system is annotated using "system-system" dimensions instead of "last-bottom" dimensions. Attachments: annotate-space.ly 740 bytes annotate-space.png 19.1 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1383 in lilypond: Make error when invoking `make maintainerclean'
Updates: Status: Fixed Labels: fixed_2_13_39 Comment #1 on issue 1383 by pnorcks: Make error when invoking `make maintainerclean' http://code.google.com/p/lilypond/issues/detail?id=1383 Pushed as http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=70a7286eb24f8445da15296c5440bb1037e21652 ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1383 in lilypond: Make error when invoking `make maintainerclean'
Status: Started Owner: pnorcks Labels: Type-Build Priority-High New issue 1383 by pnorcks: Make error when invoking `make maintainerclean' http://code.google.com/p/lilypond/issues/detail?id=1383 Original report and error message: http://lists.gnu.org/archive/html/bug-lilypond/2010-10/msg00611.html I have a fix for this and will push shortly. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Possible bug: Makefile crashed with maintainerclean
On Sun, Oct 31, 2010 at 7:05 AM, Robert Clausecker wrote: > When I execute the Lilypond-Makefile with the maintainerclean-option, I > get this error: > > $ make maintainerclean > ... lots of output ... > make --no-builtin-rules local-distclean > make[1]: Entering directory `/home/robert/lilypond' > make[1]: *** No rule to make target `/home/robert/lilypond/configure', > needed by `config.make'. Stop. > make[1]: Leaving directory `/home/robert/lilypond' > make: *** [maintainerclean] Fehler 2 > > where Fehler means error. This happens on a plain checkout of the > sourcecode and autogen afterwards. My platform is ubuntu 10.04 linux > x64, I use trunk. Thanks for the report. I've logged the bug in the tracker and will fix it shortly. http://code.google.com/p/lilypond/issues/detail?id=1383 Thanks, Patrick ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1382 in lilypond: Segfault when setting 'staff-space to 0.0
Comment #1 on issue 1382 by pnorcks: Segfault when setting 'staff-space to 0.0 http://code.google.com/p/lilypond/issues/detail?id=1382 This is a divide-by-zero problem. The patch below stops the segfault, but I'm unsure if this is the solution we want. diff --git a/lily/staff-symbol-referencer.cc b/lily/staff-symbol-referencer.cc index bec8c80..5a70b16 100644 --- a/lily/staff-symbol-referencer.cc +++ b/lily/staff-symbol-referencer.cc @@ -83,7 +83,11 @@ Staff_symbol_referencer::get_position (Grob *me) Real y = me->relative_coordinate (c, Y_AXIS) - st->relative_coordinate (c, Y_AXIS); - p += 2.0 * y / Staff_symbol::staff_space (st); + Real staff_space = Staff_symbol::staff_space (st); + if (!staff_space) + staff_space = 1; + p += 2.0 * y / staff_space; + return p; } else if (!st) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Override staff-space of zero causes a crash
On Thu, Oct 28, 2010 at 6:11 AM, Phil Holmes wrote: > Experimenting with staff-space, I set the override to zero and get a crash - > Windows, both with 2.12.3 and 2.13.36 > > \new Staff \with { \override StaffSymbol #'staff-space = #0.0 } > \relative c' { > c c c c > } Thanks, Phil. This is a divide-by-zero problem. I'm not sure of the proper fix, so I'll open a new issue and post my ideas. http://code.google.com/p/lilypond/issues/detail?id=1382 Regards, Patrick ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1382 in lilypond: Segfault when setting 'staff-space to 0.0
Status: Accepted Owner: Labels: Type-Defect Priority-Critical New issue 1382 by pnorcks: Segfault when setting 'staff-space to 0.0 http://code.google.com/p/lilypond/issues/detail?id=1382 Original report: http://lists.gnu.org/archive/html/bug-lilypond/2010-10/msg00580.html The following snippet ends with a segfault: %%% \new Staff \with { \override StaffSymbol #'staff-space = #0.0 } \relative c' { c c c c } %%% ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond 2.13.38
On Sun, Oct 31, 2010 at 7:55 AM, Graham Percival wrote: > > Bug squad: Phil is busy with the opening of a musical, so it would be > nice if somebody else could check the regression test comparisons for > both 2.13.37 and 2.13.38. It would be a shame if some horrible bug > was introduced in the past two weeks and nobody noticed. For the record, I just checked the comparisons, and everything looks fine between 2.13.37 and 2.13.38. Thanks, Patrick ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bug in rest-placement in polyphonic music
On 4 November 2010 18:55, wrote: > > Thanks. Ive read the exchange from june 2007, which is clearly > related. > > Related threads: > > http://code.google.com/p/lilypond/issues/detail?id=384 > > I cant see what happened to that. Any news? > > And the recent discussion on user: > > http://lists.gnu.org/archive/html/lilypond-user/2010-11/msg00014.html > Actually I wanted to link _your_ recent discussion on -user. But I was a bit in a hurry and I did not check twice the link I put in my e-mail. Glad to see it was actually related! Cheers, Xavier -- Xavier Scheuer ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bug in rest-placement in polyphonic music
> "X" == Xavier Scheuer writes: X> Greetings, X> Just to mention the related discussion on lilypond-user is here: X> http://lists.gnu.org/archive/html/lilypond-user/2007-06/msg00350.html X> While adding this issue to the tracker, it could be useful to add a link X> to this discussion. Thanks. Ive read the exchange from june 2007, which is clearly related. Related threads: http://code.google.com/p/lilypond/issues/detail?id=384 I cant see what happened to that. Any news? And the recent discussion on user: http://lists.gnu.org/archive/html/lilypond-user/2010-11/msg00014.html -anders ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bug in rest-placement in polyphonic music
On 4 November 2010 09:59, Anders Vinjar wrote: > >> I'm not top posting. > > \version "2.13.39" > %% rests in one voice crossing other voice > > << > {c4 c}\\ > { r8 c'' r c''} > >> > > %% Rests in mixed (rests+notes) columns don't obey Rest 'direction = #UP: > << > {c4 c}\\ > {\override Rest #'direction = #UP r8 c'' r c''} > >> > > %% wanted output > << > {c4 c}\\ > {\stemNeutral \override Stem #'neutral-direction = #UP r8 c'' r c''} > >> > > Greetings, Just to mention the related discussion on lilypond-user is here: http://lists.gnu.org/archive/html/lilypond-user/2007-06/msg00350.html While adding this issue to the tracker, it could be useful to add a link to this discussion. Cheers, Xavier -- Xavier Scheuer ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
bug in rest-placement in polyphonic music
> I'm not top posting. \version "2.13.39" %% rests in one voice crossing other voice << {c4 c}\\ { r8 c'' r c''} >> %% Rests in mixed (rests+notes) columns don't obey Rest 'direction = #UP: << {c4 c}\\ {\override Rest #'direction = #UP r8 c'' r c''} >> %% wanted output << {c4 c}\\ {\stemNeutral \override Stem #'neutral-direction = #UP r8 c'' r c''} >> ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond