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
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 agre
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-
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,
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.
_
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
> 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://
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
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 re
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://
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
"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
>
>
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.)
___
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
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 h
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 b
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 som
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
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
> ht
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...pngto
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-lilyp
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 lis
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
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".)
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
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-l
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...
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@gn
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.)
___
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
ht
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-
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
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-lil
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?
_
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-lil
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 mailin
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/listi
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
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://li
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
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 li
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://lis
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
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
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', i
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
46 matches
Mail list logo
