Re: Issue 1848 in lilypond: Lilypond-book: Give images 1mm less linewidth
Updates: Status: Fixed Labels: -Patch-needs_work Comment #1 on issue 1848 by percival.music.ca: Lilypond-book: Give images 1mm less linewidth http://code.google.com/p/lilypond/issues/detail?id=1848 93d4e8aa80360c95696e065b9fd4744f269f4ea8 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1857 in lilypond: not robust solution in spacing-loose-grace-error.ly
Comment #2 on issue 1857 by percival.music.ca: not robust solution in spacing-loose-grace-error.ly http://code.google.com/p/lilypond/issues/detail?id=1857 it was added here: 95600d78a18f28a623bc2f9ef8a7a7660d7c6e2c right after this code patch: dcdad556cddb9b88ca1c71fb093c056cc0eeda6d I agree that the proper resolution is either: 1) explain more in the texidoc 2) remove the regtest ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1845 in lilypond: Creates pure closures
Updates: Labels: -Patch-review Patch-needs_work Comment #2 on issue 1845 by colinpkc...@gmail.com: Creates pure closures http://code.google.com/p/lilypond/issues/detail?id=1845 Neil has comments on Rietveld. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1857 in lilypond: not robust solution in spacing-loose-grace-error.ly
Comment #1 on issue 1857 by k-ohara5...@oco.net: not robust solution in spacing-loose-grace-error.ly http://code.google.com/p/lilypond/issues/detail?id=1857 This is the regression test for issue 176. It uses 'strict-note-spacing, so the collision is allowed : "When strict-note-spacing is set, notes are spaced without regard for clefs, bar lines, and grace notes," It was added when single-line scores were right-justified, stretching the notes very widely, so the overlap was not seen originally. The test also causes 'programming errors' to be printed, but these are also allowed; see last few comments on issue 176. I suggest that the resolution of this issue would be to make the texidoc explain the condition for passing the test. I tried do to so but could not understand the original problem. If no-one can, a second resolution could be to remove this test. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1856 in lilypond: lots of extra space at beginning of bar
Comment #7 on issue 1856 by tdaniels...@googlemail.com: lots of extra space at beginning of bar http://code.google.com/p/lilypond/issues/detail?id=1856 Yes, the space after both key _and_ time signatures looked wrong, for the reasons I gave in comment 5. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1800 in lilypond: Segfault compiling LSR 346
Comment #10 on issue 1800 by n.putt...@gmail.com: Segfault compiling LSR 346 http://code.google.com/p/lilypond/issues/detail?id=1800 I've been intending to put the attached correction on the LSR. Thanks, I've updated the snippet. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Fix 1821: Write pathes for ly-to-tely to a separate file rather than passing as cmd line args (issue 4950053)
> Actually, with my test setup, I can't even build lilypond, because > metafont already fails with some long pathes: [...] > > Any idea? Please report this to the texl...@tug.org Werner ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1856 in lilypond: lots of extra space at beginning of bar
Comment #6 on issue 1856 by k-ohara5...@oco.net: lots of extra space at beginning of bar http://code.google.com/p/lilypond/issues/detail?id=1856 I now agree now that we want fixed space after key signatures, so that the first notes line up on successive lines. Sorry I didn't notice that earlier. Any reason to prevent the space after time signatures from stretching, through? The change would be in define-grobs.scm, under KeySignature and maybe TimeSignature and KeyCancellation, to restore "semi-fixed-space" back to "fixed-space" Attachments: stretch.png 8.5 KB nostretch.png 8.4 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1800 in lilypond: Segfault compiling LSR 346
Updates:
Status: Verified
Comment #9 on issue 1800 by k-ohara5...@oco.net: Segfault compiling LSR 346
http://code.google.com/p/lilypond/issues/detail?id=1800
This bug was the segmentation fault. Since you were able to get output,
then the bug is fixed.
The three-staff system, and resulting strange staff-change in the final
three measures, are due to some misplaced { } in th15 LSR snippet. I've
been intending
to put the attached correction on the LSR.
Attachments:
346.ly 5.0 KB
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1785 in lilypond: Compressible space before the first note of a line ?
Comment #15 on issue 1785 by k-ohara5...@oco.net: Compressible space before the first note of a line ? http://code.google.com/p/lilypond/issues/detail?id=1785 Fixed with commit cc88cd3680 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 11 in lilypond: beamlet on wrong side of tuplet sixteenth
Updates: Labels: -Patch-review Patch-needs_work Comment #16 on issue 11 by carl.d.s...@gmail.com: beamlet on wrong side of tuplet sixteenth http://code.google.com/p/lilypond/issues/detail?id=11 Hmm -- it didn't work this way for me. Apparently there's still something wrong. I'll get to it this week. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1767 in lilypond: Feta font - change breve vertical lines
"Dmytro O. Redchuk" wrote in message news:20110831151055.gz31...@volz.ua... On Wed 31 Aug 2011, 17:07 Reinhold Kainhofer wrote: Am Mittwoch, 31. August 2011, 16:56:10 schrieb Dmytro O. Redchuk: > On Sat 13 Aug 2011, 14:56 lilyp...@googlecode.com wrote: > > Updates: > > Labels: fixed_2_15_9 > > I can not change it to "Verified", because of "Issue owner must be a > project member" -- what's wrong? Nothing. Graham or someone with admin rights on the bug tracker needs to add janek to the project members on code.google.com... Ok, thank you, I will wait .) Actually, Janek has changed his email address - that old one was on the list of authors, but I deleted it when I added his new one :-o I've deleted him as owner and verified. -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1767 in lilypond: Feta font - change breve vertical lines
Updates: Status: Verified Owner: --- Comment #17 on issue 1767 by philehol...@googlemail.com: Feta font - change breve vertical lines http://code.google.com/p/lilypond/issues/detail?id=1767 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1858 in lilypond: unexplained increase in profile reports
Comment #2 on issue 1858 by d...@gnu.org: unexplained increase in profile reports http://code.google.com/p/lilypond/issues/detail?id=1858 A memory leak or significant increase in allocation need not noticeably affect performance. And it may even improve performance (some algorithms can be sped up by creating a new structure separately instead of changing an existing one in-place). But of course, if the numbers on single tests change as much as that, checking the cause would be prudent. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1858 in lilypond: unexplained increase in profile reports
Comment #1 on issue 1858 by philehol...@googlemail.com: unexplained increase in profile reports http://code.google.com/p/lilypond/issues/detail?id=1858 I'm almost 100% certain it does not relate to performance. On my Windows Vista system, 2.15.9 is _just_ slower than 2.15.7 (sorry, don't have 15.8). The attached image shows the ratio between timing for all the regression tests - as you'll see, there's more above 100% than below, but overall the newer version is only 7% slower for all 998 tests. Attachments: LilyTimings.png 6.6 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1767 in lilypond: Feta font - change breve vertical lines
On Wed 31 Aug 2011, 17:07 Reinhold Kainhofer wrote: > Am Mittwoch, 31. August 2011, 16:56:10 schrieb Dmytro O. Redchuk: > > On Sat 13 Aug 2011, 14:56 lilyp...@googlecode.com wrote: > > > Updates: > > > Labels: fixed_2_15_9 > > > > I can not change it to "Verified", because of "Issue owner must be a > > project member" -- what's wrong? > > Nothing. Graham or someone with admin rights on the bug tracker needs to add > janek to the project members on code.google.com... Ok, thank you, I will wait .) -- Dmytro O. Redchuk"Easy to use" is easy to say. Bug Squad -- Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1767 in lilypond: Feta font - change breve vertical lines
Am Mittwoch, 31. August 2011, 16:56:10 schrieb Dmytro O. Redchuk: > On Sat 13 Aug 2011, 14:56 lilyp...@googlecode.com wrote: > > Updates: > > Labels: fixed_2_15_9 > > I can not change it to "Verified", because of "Issue owner must be a > project member" -- what's wrong? Nothing. Graham or someone with admin rights on the bug tracker needs to add janek to the project members on code.google.com... Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1783 in lilypond: Spaces in filenames don't work with -danti-alias-factor option
Updates: Status: Verified Comment #4 on issue 1783 by brownian.box: Spaces in filenames don't work with -danti-alias-factor option http://code.google.com/p/lilypond/issues/detail?id=1783 For the record: %-8<--- This means that the lilypond build of the release didn't compile libpng with version info included. Since that library is not installed system-wise, I don't see a problem there. Cheers, Reinhold %-8<--- ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1767 in lilypond: Feta font - change breve vertical lines
On Sat 13 Aug 2011, 14:56 lilyp...@googlecode.com wrote: > Updates: > Labels: fixed_2_15_9 I can not change it to "Verified", because of "Issue owner must be a project member" -- what's wrong? > Comment #16 on issue 1767 by n.putt...@gmail.com: Feta font - change > breve vertical lines > http://code.google.com/p/lilypond/issues/detail?id=1767 > > (No comment was entered for this change.) -- Dmytro O. Redchuk"Easy to use" is easy to say. Bug Squad -- Jeff Garbers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1783 in lilypond: Spaces in filenames don't work with -danti-alias-factor option
Am Mittwoch, 31. August 2011, 15:28:23 schrieb lilyp...@googlecode.com: > Comment #3 on issue 1783 by brownian.box: Spaces in filenames don't work > with -danti-alias-factor option > http://code.google.com/p/lilypond/issues/detail?id=1783 > > I have got this warning: > > Converting to PNG...pngtopnm: /home/dor/lilypond/usr/lib/libpng12.so.0: no > version information available (required by pngtopnm) This means that the lilypond build of the release didn't compile libpng with version info included. Since that library is not installed system-wise, I don't see a problem there. Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org signature.asc Description: This is a digitally signed message part. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1777 in lilypond: adds auto-generated documentation for context modifications
Updates: Status: Verified Comment #5 on issue 1777 by brownian.box: adds auto-generated documentation for context modifications http://code.google.com/p/lilypond/issues/detail?id=1777 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1779 in lilypond: accidentaled notes too far from the barline
Updates: Status: Verified Comment #16 on issue 1779 by brownian.box: accidentaled notes too far from the barline http://code.google.com/p/lilypond/issues/detail?id=1779 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1783 in lilypond: Spaces in filenames don't work with -danti-alias-factor option
Comment #3 on issue 1783 by brownian.box: Spaces in filenames don't work with -danti-alias-factor option http://code.google.com/p/lilypond/issues/detail?id=1783 I have got this warning: Converting to PNG...pngtopnm: /home/dor/lilypond/usr/lib/libpng12.so.0: no version information available (required by pngtopnm) Is it ok? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1785 in lilypond: Compressible space before the first note of a line ?
Comment #14 on issue 1785 by brownian.box: Compressible space before the first note of a line ? http://code.google.com/p/lilypond/issues/detail?id=1785 Please, which commit ID? (I usually ask for this if an issue does not contain any "formal code to verify".) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Fix 1821: Write pathes for ly-to-tely to a separate file rather than passing as cmd line args (issue 4950053)
Am Mittwoch, 31. August 2011, 06:26:59 schrieb percival.music...@gmail.com: > sweet mao that's disgusting. I love it. :) > > If you can make doc from scratch, then push. Actually, with my test setup, I can't even build lilypond, because metafont already fails with some long pathes: I created the path "/data/lilypond/This-is-a-very-long-path-to-the-lilypond- source-directory/And-it-contains-several-long-sub-directories/Which-should- break-the-makefile/Because-the-call-to-lys-to-telys-will-be-longer-than-the- allowed-13-characters/" and symlinked my lilypond sourcedir there. Then I configured an out-of-source build in /data/lilypond/build1 and ran make. The binary built fine, but metapost fails with a memory corruption in glibc! In particular: lilypond@curie:~/build1/mf/out$ mpost -progname=mpost -ini /data/lilypond/This-is-a-very-long-path-to-the-lilypond-source-directory/And- it-contains-several-long-sub-directories/Which-should-break-the- makefile/Because-the-call-to-lys-to-telys-will-be-longer-than-the- allowed-13-characters/lilypond/mf/mf2pt1.mp \\dump This is MetaPost, version 1.208 (kpathsea version 5.0.0) (INIMP) (/data/lilypond/This-is-a-very-long-path-to-the-lilypond-source-directory/And- i t-contains-several-long-sub-directories/Which-should-break-the- makefile/Because -the-call-to-lys-to-telys-will-be-longer-than-the-allowed-13- characters/lil ypond/mf/mf2pt1.mp*** glibc detected *** mpost: double free or corruption (!prev): 0x0a0ebab0 *** === Backtrace: = /lib/i386-linux-gnu/libc.so.6(+0x6b961)[0x17b961] /lib/i386-linux-gnu/libc.so.6(+0x6d28b)[0x17d28b] /lib/i386-linux-gnu/libc.so.6(cfree+0x6d)[0x18041d] mpost[0x80625f1] mpost[0x8062686] mpost[0x8077f90] mpost[0x808c08b] mpost[0x804ad3d] /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x126e37] mpost[0x80495f1] === Memory map: 0011-0026a000 r-xp 08:01 1097937/lib/i386-linux- gnu/libc-2.13.so 0026a000-0026b000 ---p 0015a000 08:01 1097937/lib/i386-linux- gnu/libc-2.13.so 0026b000-0026d000 r--p 0015a000 08:01 1097937/lib/i386-linux- gnu/libc-2.13.so [...] Any idea? Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1811 in lilypond: Revise warning re cueDuring font size
Updates: Status: Verified Comment #8 on issue 1811 by brownian.box: Revise warning re cueDuring font size http://code.google.com/p/lilypond/issues/detail?id=1811 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1816 in lilypond: Lilypond-book music runs off right side of the page
Updates: Labels: -fixed_2_15_9 fixed_2_15_10 Comment #16 on issue 1816 by reinhold...@gmail.com: Lilypond-book music runs off right side of the page http://code.google.com/p/lilypond/issues/detail?id=1816 Ah, sorry, I missed that Graham has released 2.15.9 meanwhile... ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1811 in lilypond: Revise warning re cueDuring font size
Comment #7 on issue 1811 by colinpkc...@gmail.com: Revise warning re cueDuring font size http://code.google.com/p/lilypond/issues/detail?id=1811 The commit id is 82f8daa538dd4b5549219feff6a8c65bc4e46cb ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1790 in lilypond: Proper loglevels: cmd-line option --loglevel=NONE/ERROR/WARN/PROGRESS/INFO/DEBUG
Updates: Status: Verified Comment #11 on issue 1790 by brownian.box: Proper loglevels: cmd-line option --loglevel=NONE/ERROR/WARN/PROGRESS/INFO/DEBUG http://code.google.com/p/lilypond/issues/detail?id=1790 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1792 in lilypond: dot-notehead collision
Updates: Status: Verified Comment #6 on issue 1792 by brownian.box: dot-notehead collision http://code.google.com/p/lilypond/issues/detail?id=1792 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1794 in lilypond: Adds longas, maximas and non-standard tweaks to MultiMeasureRest
Updates: Status: Verified Comment #5 on issue 1794 by brownian.box: Adds longas, maximas and non-standard tweaks to MultiMeasureRest http://code.google.com/p/lilypond/issues/detail?id=1794 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1796 in lilypond: LilyPond segfaults on make-footer = ##f
Updates: Status: Verified Comment #4 on issue 1796 by brownian.box: LilyPond segfaults on make-footer = ##f http://code.google.com/p/lilypond/issues/detail?id=1796 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1799 in lilypond: output-distance.py does not parse scheme nan values correctly
Updates: Status: Verified Comment #7 on issue 1799 by brownian.box: output-distance.py does not parse scheme nan values correctly http://code.google.com/p/lilypond/issues/detail?id=1799 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1800 in lilypond: Segfault compiling LSR 346
Comment #8 on issue 1800 by brownian.box: Segfault compiling LSR 346 http://code.google.com/p/lilypond/issues/detail?id=1800 2.15.9 gives three-staff-system for that snippet. Last three measures are "strange". Is this ok? Should it become another issue? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1807 in lilypond: Adds a lyric tie glyph to feta font
Updates: Status: Verified Comment #4 on issue 1807 by brownian.box: Adds a lyric tie glyph to feta font http://code.google.com/p/lilypond/issues/detail?id=1807 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1808 in lilypond: [PATCH] Implement MusicXML files in lilypond-book
Updates: Status: Verified Comment #3 on issue 1808 by brownian.box: [PATCH] Implement MusicXML files in lilypond-book http://code.google.com/p/lilypond/issues/detail?id=1808 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1811 in lilypond: Revise warning re cueDuring font size
Comment #6 on issue 1811 by brownian.box: Revise warning re cueDuring font size http://code.google.com/p/lilypond/issues/detail?id=1811 Please, which commit ID? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1813 in lilypond: Doc: Overlapping boxes and section headers in LM
Updates: Status: Verified Comment #6 on issue 1813 by brownian.box: Doc: Overlapping boxes and section headers in LM http://code.google.com/p/lilypond/issues/detail?id=1813 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1816 in lilypond: Lilypond-book music runs off right side of the page
Comment #15 on issue 1816 by brownian.box: Lilypond-book music runs off right side of the page http://code.google.com/p/lilypond/issues/detail?id=1816 I believe "fixed_2_15_9" is wrong. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1847 in lilypond: Lilypond-book: Get rid of lilyquote option, use quote instead
Comment #4 on issue 1847 by reinhold...@gmail.com: Lilypond-book: Get rid of lilyquote option, use quote instead http://code.google.com/p/lilypond/issues/detail?id=1847 Commits aeca8fad67c65a7d6e8a6e943d0d9f050e6a67c5 (code) and 4ca01b6da8d60b0d8575be05ae974429c91becd5 (changes all snippts in the docs) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1824 in lilypond: DOC: revise CG instructions for commit access
Updates: Status: Verified Comment #3 on issue 1824 by brownian.box: DOC: revise CG instructions for commit access http://code.google.com/p/lilypond/issues/detail?id=1824 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1847 in lilypond: Lilypond-book: Get rid of lilyquote option, use quote instead
Comment #3 on issue 1847 by brownian.box: Lilypond-book: Get rid of lilyquote option, use quote instead http://code.google.com/p/lilypond/issues/detail?id=1847 Please, which commit ID? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1820 in lilypond: recent commit breaks GUB
Updates: Status: Verified Comment #4 on issue 1820 by brownian.box: recent commit breaks GUB http://code.google.com/p/lilypond/issues/detail?id=1820 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1843 in lilypond: Creates a Flag grob
Updates: Status: Verified Comment #2 on issue 1843 by brownian.box: Creates a Flag grob http://code.google.com/p/lilypond/issues/detail?id=1843 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1858 in lilypond: unexplained increase in profile reports
On Aug 31, 2011, at 8:50 AM, lilyp...@googlecode.com wrote: > Status: Accepted > Owner: > Labels: Type-Critical Regression > > New issue 1858 by k-ohara5...@oco.net: unexplained increase in profile reports > http://code.google.com/p/lilypond/issues/detail?id=1858 > > The reported 'cells', in the profile output for the regression tests, doubled > for several tests between 2.15.8 and 2.15.9. > > "lyric-tie.profile" was in 2.15.8 > time: 0 > cells: 1125395 > I remember seeing a hike because of my stem work in certain regtests, but it was of a factor of about 1.15 and was due to the presence of beams and the caching of their pure heights. I fixed this in part with my change to item.cc, but this could still be problematic. Is there any way to get a chart breaking down what grobs are doing the cell accessing? Cheers, MS ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1856 in lilypond: lots of extra space at beginning of bar
Comment #5 on issue 1856 by tdaniels...@googlemail.com: lots of extra space at beginning of bar http://code.google.com/p/lilypond/issues/detail?id=1856 In my opinion the large space after key signature and time signature on sparsely populated lines is wrong. The notes are displaced too far from their position in the bar in comparison with lines following which have no prefatory matter. So I agree this is a critical regression and my vote is for reverting cc88cd3680. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
