Comment #19 on issue 1152 by pnorcks: Regression: collisions with
accidentals
http://code.google.com/p/lilypond/issues/detail?id=1152
You're not doing anything wrong. It's a recent problem with Google code
hosting:
http://code.google.com/p/support/issues/detail?id=4266
Updates:
Labels: Patch
Comment #11 on issue 442 by n.puttock: Enhancement: RemoveEmptyStaffContext
shouldn't reduce PianoStaff to one staff
http://code.google.com/p/lilypond/issues/detail?id=442
(No comment was entered for this change.)
__
Updates:
Summary: LilyPond crash when using showFirstLength/showLastLength with
\compressFullBarRests
Comment #6 on issue 1173 by n.puttock: LilyPond crash when using
showFirstLength/showLastLength with \compressFullBarRests
http://code.google.com/p/lilypond/issues/detail?id=1173
(No comm
Comment #4 on issue 1193 by n.puttock: [PATCH] Enhancement: internal ledger
lines
http://code.google.com/p/lilypond/issues/detail?id=1193
(No comment was entered for this change.)
Attachments:
internal-legers.png 1.4 KB
___
bug-lilypond
Comment #3 on issue 1193 by n.puttock: [PATCH] Enhancement: internal ledger
lines
http://code.google.com/p/lilypond/issues/detail?id=1193
Cleaned up patch: http://codereview.appspot.com/1855056/show
I've removed the code associated with chromatic staves, since Kevin Dalley
produced a separ
Updates:
Status: Started
Owner: jan.nieuwenhuizen
Comment #22 on issue 684 by n.puttock: Enhancement: MetronomeMark should
support break-align-symbols
http://code.google.com/p/lilypond/issues/detail?id=684
(No comment was entered for this change.)
___
Updates:
Status: Started
Labels: Patch
Comment #5 on issue 1173 by n.puttock: LilyPond crash when using
showLastLength with \compressFullBarRests
http://code.google.com/p/lilypond/issues/detail?id=1173
Mike Solomon has started work on this:
http://codereview.appspot.com/1741
On Wed, Aug 04, 2010 at 07:50:01PM +, Robert Kennedy wrote:
> > Several extender bugs were fixed in recent 2.13 releases, but I don't
> > think we can backport them since there's unlikely to be another 2.12
> > release.
>
> When is a stable 2.13 release planned?
There will never be a stable 2
On 4 August 2010 20:50, Robert Kennedy wrote:
> Just out of curiosity, how does an infinite loop turn into a segmentation
> fault?
I'm not entirely sure, but it seems the loop runs out of memory on the
stack eventually, causing an access violation.
> When is a stable 2.13 release planned?
A s
Neil Puttock gmail.com> writes:
> Here's a minimal snippet:
>
> \version "2.12.3"
> <<
> \new Voice = melody { c4 c8 }
> \new Voice = tenorVerses { c2 }
>
> \context Lyrics = foo \lyricsto dummy {
> la
> }
> \context Lyrics = foo \lyricsto melody {
> la __
> }
> >>
Nice! Tha
On 4 August 2010 18:59, James Bailey wrote:
> I don't know if it helps, but using the development version there is no
> segmentation fault. Additionally, adding ~ to the third beat in:
> gis8 gis8~ gis8 fis8~ fis e8~ e e~ |
>
> also gets rid of the problem
Here's a minimal snippet:
\version "
On 4 August 2010 18:59, James Bailey wrote:
> I don't know if it helps, but using the development version there is no
> segmentation fault. Additionally, adding ~ to the third beat in:
> gis8 gis8~ gis8 fis8~ fis e8~ e e~ |
>
> also gets rid of the problem
Here's a minimal snippet:
\version "
> I don't know if it helps, but using the development version there is no
> segmentation fault.
It might help me if I run into the problem and am not able to work around it in
2.12.3; thanks!
You might also want to check whether this bug was actually fixed in 2.13 or
just
hidden by accident. Ev
James Bailey googlemail.com> writes:
> Okay, in just scanning the file, I was a bit concerned about that.
> I think actually a smaller example would be
> better. If you can pare this down just a bit, I'll be happy to add
> it to the tracker.
Of course a smaller example would be nice, but I alrea
Updates:
Labels: -Priority-High Priority-Critical Regression
Comment #1 on issue 1198 by n.puttock: Display method for \time broken
http://code.google.com/p/lilypond/issues/detail?id=1198
Oh well, 2.13.29 arrived sooner than expected. :)
Test 93 unequal: .
in = \time 2/4
out = \context
On 4 August 2010 08:54, Graham Percival wrote:
> One of your vital tasks -- arguably even more important than
> replying to emails -- is to check the regtest comparison for every
> release.
There's something fishy about the latest comparisons: a number of .log
changes suggest broken regtests, and
On Aug 4, 2010, at 6:51 PM, Robert Kennedy wrote:
>> I'm also an on-duty bug squadder, and I am running OSX. I have a
>> question, where is nonexistentVoice defined?
>
> It's not. I am able to reproduce (what appears to be) the same crash
> with a perfectly valid lilypond source file in which ev
On Aug 4, 2010, at 6:51 PM, Robert Kennedy wrote:
>> I'm also an on-duty bug squadder, and I am running OSX. I have a
>> question, where is nonexistentVoice defined?
>
> It's not. I am able to reproduce (what appears to be) the same crash
> with a perfectly valid lilypond source file in which ev
Ralph Palmer gmail.com> writes:
> As today's assigned Bug Squad member, I would check this and, if confirmed,
> add it as an issue. However, I have no access to the OS X operating system.
> Could someone else on the Bug Squad please check it?
The problem is not OS X-specific. I just checked on li
On Jul 31, 2010, at 3:44 PM, P. Baguis wrote:
> Hi, I tried to use LilyPond on a Powerbook (PPC) running Mac OS X 10.3.9 but
> the
> application fails to launch. I receive an error message about an "undefined
> reference to _mmap$UNIX2003".
>
> Is there anything I can do to make it work?
>
>
On Aug 4, 2010, at 6:56 AM, Robert Kennedy wrote:
>> I am not top-posting.
>
> Sorry I'm not able to make the source file below any shorter; it seems like
> if I
> take anything out, the bug doesn't manifest.
>
> $ /Applications/LilyPond.app/Contents/Resources/bin/lilypond bug3.ly
> GNU LilyPo
Yes, that solved my problem with the lyrics.
Tricky this kind of things, because a measure follows the measure giving me a
headache.
Sorry that I got the wrong list, but it seemed to me that it was an
"undocumented" feature...
Thanks anyway.
Herman Grootaers
__
Greetings -
As today's assigned Bug Squad member, I would check this and, if confirmed,
add it as an issue. However, I have no access to the OS X operating system.
Could someone else on the Bug Squad please check it?
Ralph
On Wed, Aug 4, 2010 at 12:56 AM, Robert Kennedy wrote:
> > I am not top-
One of your vital tasks -- arguably even more important than
replying to emails -- is to check the regtest comparison for every
release.
If you've read anything that looks relevant and was linked to
directly from the CG chapter on Issues, and don't know how to do
this, then clearly we need to talk
24 matches
Mail list logo
