Comment #1 on issue 1155 by i...@hulin.org.uk: remove MODULE_GC_KLUDGE
blocks from the code base
http://code.google.com/p/lilypond/issues/detail?id=1155
A patch is available for review on Rietveld URL:
http://codereview.appspot.com/1744042
Cheers,
Ian
_
Hi Patrick,
On 26/06/10 02:43, Patrick McCarty wrote:
On Mon, May 17, 2010 at 10:43 AM, Ian Hulin wrote:
We have these blocks in our C++ code base:
$ git grep -A 5 MODULE_GC_KLUDGE
lily/include/ly-module.hh:#define MODULE_GC_KLUDGE
lily/include/ly-module.hh-
lily/include/ly-module.hh-#endi
Updates:
Status: Fixed
Labels: fixed_2_13_27
Comment #1 on issue 1117 by n.puttock: PATCH Woodwind diagrams
(issue1425041)
http://code.google.com/p/lilypond/issues/detail?id=1117
(No comment was entered for this change.)
___
bug-li
Updates:
Labels: -Type-Defect -Priority-Medium Type-Enhancement Priority-Low
Comment #1 on issue 1134 by n.puttock: Notes in different voices do not
treat accidentals properly
http://code.google.com/p/lilypond/issues/detail?id=1134
This is a documented limitation of the Accidental_eng
Updates:
Status: Invalid
Comment #1 on issue 1137 by n.puttock: \bassFigureExtendersOn regression
http://code.google.com/p/lilypond/issues/detail?id=1137
The spacing for `Text' is an improvement (from issue 1120).
___
bug-lilypond mailing lis
Updates:
Status: Fixed
Labels: fixed_2_13_26
Comment #9 on issue 1123 by pnorcks: 16th and shorter notes (not beamed)
have ugly defects
http://code.google.com/p/lilypond/issues/detail?id=1123
This problem was fixed as a result of the fontforge update in GUB.
Updates:
Labels: Patch
Comment #4 on issue 804 by n.puttock: Code cleaning: checking
types-conversion issues and other build warnings
http://code.google.com/p/lilypond/issues/detail?id=804
http://codereview.appspot.com/1724041/show
___
bug
Comment #3 on issue 804 by n.puttock: Code cleaning: checking
types-conversion issues and other build warnings
http://code.google.com/p/lilypond/issues/detail?id=804
Issue 1144 has been merged into this issue.
___
bug-lilypond mailing list
bug-lil
Updates:
Status: Duplicate
Mergedinto: 804
Comment #1 on issue 1144 by n.puttock: [PATCH] 100+ warnings (issue1724041)
http://code.google.com/p/lilypond/issues/detail?id=1144
(No comment was entered for this change.)
___
bug-lilypond
Updates:
Summary: \chordmode neglects point-and-click
Comment #2 on issue 1022 by n.puttock: \chordmode neglects point-and-click
http://code.google.com/p/lilypond/issues/detail?id=1022
(No comment was entered for this change.)
___
bug-lilypon
Updates:
Labels: -Regression
Comment #7 on issue 997 by n.puttock: RehearsalMarks are not kept inside
the page
http://code.google.com/p/lilypond/issues/detail?id=997
(No comment was entered for this change.)
___
bug-lilypond mailing list
b
Updates:
Labels: -Priority-Critical -Regression Priority-Medium
Comment #2 on issue 1149 by n.puttock: Uneven spacing with uniform
stretching
http://code.google.com/p/lilypond/issues/detail?id=1149
There's no regression here, since there's only one relevant change between
2.12 and 2
Comment #7 on issue 1156 by pnorcks: Continuing slur across line containing
only spacer rests leads to allocation error
http://code.google.com/p/lilypond/issues/detail?id=1156
Okay, thanks. I've pushed the changes.
___
bug-lilypond mailing list
b
Comment #6 on issue 1156 by n.puttock: Continuing slur across line
containing only spacer rests leads to allocation error
http://code.google.com/p/lilypond/issues/detail?id=1156
Exactly. :)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http:/
Comment #5 on issue 1156 by pnorcks: Continuing slur across line containing
only spacer rests leads to allocation error
http://code.google.com/p/lilypond/issues/detail?id=1156
Thanks Neil. Is this what you have in mind?
diff --git a/lily/slur-scoring.cc b/lily/slur-scoring.cc
index a1f761a.
Comment #4 on issue 1156 by n.puttock: Continuing slur across line
containing only spacer rests leads to allocation error
http://code.google.com/p/lilypond/issues/detail?id=1156
Hi Patrick,
Sometimes the check for the *left* broken neighbor may be a spacer rest,
which appears to be a generi
Updates:
Status: Fixed
Owner: pnorcks
Labels: fixed_2_13_27
Comment #3 on issue 1156 by pnorcks: Continuing slur across line containing
only spacer rests leads to allocation error
http://code.google.com/p/lilypond/issues/detail?id=1156
Thanks for the report.
This was
On Sun, Jun 27, 2010 at 06:48:09PM +0100, Phil Holmes wrote:
> I was looking at http://lilypond.org/install/#2.12 - which I wouldn't have
> thought was an old unsupported website - it's the main download page.
Like it or not, that's the old unsupported website.
> I
> know there's an issue report
I was looking at http://lilypond.org/install/#2.12 - which I wouldn't have
thought was an old unsupported website - it's the main download page. I
know there's an issue report to get rid of claimed support for ME and NT
(http://code.google.com/p/lilypond/issues/detail?id=809) and I think Windows
I think we could say, therefore, that it runs on Windows in the same way as
it does on Vista and XP, which I run. I'd guess the long uninstall time is
more of an issue for the development team, who need to keep up to date with
the latest version, than it is for the general user. I have experienc
"Phil Holmes" wrote in message
news:i05ajd$18...@dough.gmane.org...
wrote in message
news:14-9567054385019064696-7381504033751444317-lilypond=googlecode@googlecode.com...
Comment #14 on issue 989 by percival.music.ca: ensure that no information
is only in the regtests
http://code.google
On 6/26/10 10:36 AM, "Phil Holmes" wrote:
>> "Carl Sorensen" wrote in message
>> news:c84b8617.136ad%c_soren...@byu.edu...
>>
>>
>>
>> On 6/26/10 4:38 AM, "Phil Holmes" wrote:
>>
>>> "Ben Englert" wrote in message
File follows:
\version "2.13.21"
PartPOn
Updates:
Summary: Continuing slur across line containing only spacer rests leads to
allocation error
Comment #2 on issue 1156 by Carl.D.Sorensen: Continuing slur across line
containing only spacer rests leads to allocation error
http://code.google.com/p/lilypond/issues/detail?id=1156
This
"Ben Englert" wrote in message
news:loom.20100627t041238...@post.gmane.org...
I'm not top posting
Phil is correct in that these lines were culled from a much larger file
with
trial-and-error. However, I've done another pass evaluating what
elements can be removed from each linewhile still repr
Comment #1 on issue 1156 by PhilEHolmes: Memory allocation problem
http://code.google.com/p/lilypond/issues/detail?id=1156
Updated minimal version of the source file producing the problem from the
original reporter Ben Englert. He reports he can't make this smaller and
still reproduce the p
Hi,
On Sat, 26 Jun 2010 19:20:55 +0200, Joe Neeman wrote:
Thanks, I've reverted the patch in the meantime. However, the
information that you see in annotate-spacing is actually computed after
line-breaking,
ok, so why can't it then be taken into account for page-breaking?
i mean, for me it s
26 matches
Mail list logo
