Comment #8 on issue 1613 by k-ohara5...@oco.net: Beamed stems too long when
avoiding low note in other voice
http://code.google.com/p/lilypond/issues/detail?id=1613
The discussion concerns whether to
1) do not try to avoid stems (previous behavior, which would un-fix issue
795) or
2) build
Updates:
Status: Fixed
Labels: fixed_2_15_0 backport
Comment #4 on issue 1632 by k-ohara5...@oco.net: beam staff change weird
angular beam
http://code.google.com/p/lilypond/issues/detail?id=1632
Commit f9116bac3 did resolve this problem in builds from git (but the fix
did no
Updates:
Status: Fixed
Labels: fixed_2_15_0 backport
Comment #23 on issue 1612 by k-ohara5...@oco.net: Change staff produces
long stems
http://code.google.com/p/lilypond/issues/detail?id=1612
The original example (not comment 17 which is moved to issue 1632) started
working
Phil Holmes wrote:
>There are 2 bugs against glissandi in 13.61 - 1639 and 1640. I would
>assume your problem is related.
Maybe not.
The two bugs are fixed:
http://codereview.appspot.com/4457042
But I still get the same error using the latest sources... version
2.15.0 (?!?).
Please reply to al
On 5/2/11 7:48 AM, "m...@apollinemike.com" wrote:
> On May 2, 2011, at 5:21 AM, lilyp...@googlecode.com wrote:
>
>>
>> Comment #19 on issue 1612 by brownian.box: Change staff produces long stems
>> http://code.google.com/p/lilypond/issues/detail?id=1612
>>
>> I have missed something very pr
On May 2, 2011, at 5:21 AM, lilyp...@googlecode.com wrote:
>
> Comment #19 on issue 1612 by brownian.box: Change staff produces long stems
> http://code.google.com/p/lilypond/issues/detail?id=1612
>
> I have missed something very probably, but: this issue is of type "Collision"
> (not "Doc") st
Comment #22 on issue 1612 by byu9...@gmail.com: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
Once things have settled down, I'll backport the whole set. But I'm
waiting a bit.
Thanks,
Carl
___
bug
Updates:
Labels: backport
Comment #5 on issue 1615 by percival.music.ca: lily-git.tcl not working:
savannah sometimes does not like git fetch --depth
http://code.google.com/p/lilypond/issues/detail?id=1615
carl, could you backport:
c2fea503702f24a66c672aa7999696cafa292021
again, I do
Updates:
Summary: lily-git.tcl not working: savannah sometimes does not like git
fetch --depth
Comment #4 on issue 1615 by percival.music.ca: lily-git.tcl not working:
savannah sometimes does not like git fetch --depth
http://code.google.com/p/lilypond/issues/detail?id=1615
I've added a w
Comment #3 on issue 1615 by percival.music.ca: lily-git.tcl not working:
savannah no longer likes git fetch --depth
http://code.google.com/p/lilypond/issues/detail?id=1615
mao, so it's some intermittent thing. (I'm seeing about 10% success from
both university and home, but apparently most
Updates:
Status: Verified
Comment #5 on issue 1600 by percival.music.ca: Allows users to request that
beam collision occur on the Voice level
http://code.google.com/p/lilypond/issues/detail?id=1600
nah, this is a patch. If you don't have git, then ignore it. If you have
git, then
Comment #21 on issue 1612 by percival.music.ca: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
I'm guessing that my comment 18 about "already pushed his patches" is
referring to some subset (not necessarily a proper subset, though) of:
275ef7f1fdbe
Updates:
Status: Verified
Comment #11 on issue 1620 by colinpkc...@gmail.com: Midi overflow with
instrument changes
http://code.google.com/p/lilypond/issues/detail?id=1620
Verified 2.13.61, after changing \version in aa.ly from 2.12, which warned
about not finding proerty type-check
Updates:
Status: Accepted
Labels: -fixed_2_13_61
Comment #20 on issue 1612 by percival.music.ca: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
"what's wrong"? What's wrong is that the initial snippet causes the same
problem in the
Updates:
Status: Fixed
Comment #12 on issue 1633 by percival.music.ca: pdf utf-16be breaks doc
compile
http://code.google.com/p/lilypond/issues/detail?id=1633
Colin: with all the confusion about branches, I think we should get
stricter about verifying. The guidelines have changed:
Updates:
Status: Verified
Comment #11 on issue 1605 by brownian.box: PS -> PDF conversion fails
http://code.google.com/p/lilypond/issues/detail?id=1605
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-lilypond@gnu.o
Comment #4 on issue 1600 by brownian.box: Allows users to request that beam
collision occur on the Voice level
http://code.google.com/p/lilypond/issues/detail?id=1600
Test file please.)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://li
Updates:
Status: Fixed
Labels: -Patch-review fixed_2_15_0
Comment #5 on issue 1626 by percival.music.ca: Articulate produces faulty
barcheck warnings
http://code.google.com/p/lilypond/issues/detail?id=1626
pushed
d4c5b03afa8384ee50a7b9536485bc26d14033aa
_
Updates:
Status: Verified
Comment #8 on issue 1619 by brownian.box: Incorrect beam/stem
http://code.google.com/p/lilypond/issues/detail?id=1619
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https
Comment #19 on issue 1612 by brownian.box: Change staff produces long stems
http://code.google.com/p/lilypond/issues/detail?id=1612
I have missed something very probably, but: this issue is of
type "Collision" (not "Doc") still _and_ the initial snippet produces the
very same picture with 2.
Updates:
Status: Verified
Comment #5 on issue 1636 by brownian.box: midiVolume 0.0 not respected
http://code.google.com/p/lilypond/issues/detail?id=1636
Verified with 2.13.61, thank you!
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http
Updates:
Status: Verified
Comment #10 on issue 1624 by brownian.box: Segfault with stabel and
development versions
http://code.google.com/p/lilypond/issues/detail?id=1624
Yes, verified with 2.13.61, THANKS .)
___
bug-lilypond mailing list
Comment #9 on issue 1624 by anna.kuz...@gmail.com: Segfault with stabel and
development versions
http://code.google.com/p/lilypond/issues/detail?id=1624
Verified with 2.13.61, THANKS!
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://list
On 01. mai 2011 19:24, lilyp...@googlecode.com wrote:
Comment #4 on issue 1626 by percival.music.ca: Articulate produces
faulty barcheck warnings
http://code.google.com/p/lilypond/issues/detail?id=1626
does anybody have an email address for Helge Hafting? I'd like to make
Both helge.haft...@hi
24 matches
Mail list logo
