Updates:
Status: Verified
Comment #4 on issue 1694 by colinpkc...@gmail.com: Modifies
Spanner::spanner_length to better handle line-spanners
http://code.google.com/p/lilypond/issues/detail?id=1694
verified 2.15.3
___
bug-lilypond mailing l
Updates:
Status: Verified
Comment #6 on issue 1697 by colinpkc...@gmail.com: Add ties from
Completion_note_heads_engraver to a TieColumn
http://code.google.com/p/lilypond/issues/detail?id=1697
(No comment was entered for this change.)
___
On 11-06-28 11:00 AM, Valentin Villenave wrote:
Greetings Bug Squad,
I've been looking at the tracker and known issues, but I couldn't find
this one. Is this considered normal behavior?
\version "2.15.3"
<<
\new Staff = "up" { s1 }
\new Staff = "down"
\relative c' {
c8( \chang
Status: Accepted
Owner:
Labels: Type-Collision Priority-High
New issue 1718 by colinpkc...@gmail.com: Slur collides with cross-staff
stems
http://code.google.com/p/lilypond/issues/detail?id=1718
Reported by Valentin Villenave:
I've been looking at the tracker and known issues, but I coul
> There's nothing attached, but it's in git:
> db6910b2913115769ba736e0b0ff6a159ba4
> http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=db6910b2913115769ba736e0b0ff6a159ba4
Thanks.
> Unfortunately it just missed the 2.15.3 release, but it will be
> included in 2.15.4.
Ok.
Updates:
Status: Verified
Comment #8 on issue 1467 by colinpkc...@gmail.com: [PATCH] Doc: Rewrite NR
3.2 Titles and headers. (issue3667041)
http://code.google.com/p/lilypond/issues/detail?id=1467
(No comment was entered for this change.)
_
Updates:
Status: Verified
Comment #3 on issue 1014 by colinpkc...@gmail.com: Full/multi measure rests
should be semibreve (for any but 4/2)
http://code.google.com/p/lilypond/issues/detail?id=1014
(No comment was entered for this change.)
_
=On 6/28/11 12:30 PM, "Federico Bruni" wrote:
> Il giorno lun, 27/06/2011 alle 13.13 -0600, Carl Sorensen ha scritto:
>> I'm trying to get ready for release 2.14.2. In general, I'd like
>> bugfixes
>> from 2.15.x to show up in 2.14.2.
>
> Carl,
>
> when v2.14.2 will be released? (more or less)
Updates:
Status: Fixed
Labels: fixed_2_15_4
Comment #6 on issue 1714 by percival.music.ca: Build error regarding mf2pt1
with latest texlive (2011) and lilypond
http://code.google.com/p/lilypond/issues/detail?id=1714
(No comment was entered for this change.)
_
(Note: this message is in reply to an existing thread. I just subscribed
to the ML. I apologize if this creates a new thread.)
Thank you for clarifying the problem surrounding mpost.
> Attached is a fix which makes it work again in lilypond (without
> breaking backwards compatibility to older mpo
Comment #5 on issue 1714 by marc...@gmail.com: Build error regarding mf2pt1
with latest texlive (2011) and lilypond
http://code.google.com/p/lilypond/issues/detail?id=1714
I built lilypond shortly after that commit and had no problems, so I think
it's fixed.
_
Greetings everybody,
some translated doc pages have broken @snippet links; for example if
you follow the link at the bottom of
http://lilypond.org/doc/v2.15/Documentation/notation/expressive-marks-as-curves.de.html
you'll see that it points to
http://lilypond.org/doc/v2.15/Documentation/snippets/a
Greetings Bug Squad,
I've been looking at the tracker and known issues, but I couldn't find
this one. Is this considered normal behavior?
\version "2.15.3"
<<
\new Staff = "up" { s1 }
\new Staff = "down"
\relative c' {
c8( \change Staff = "up"
c' c \change Staff = "down"
Updates:
Labels: -Patch-new Patch-review
Comment #2 on issue 1259 by pkx1...@gmail.com: DynamicTextSpanner #'style =
#'none doesn't work over \break
http://code.google.com/p/lilypond/issues/detail?id=1259
Passes reg tests - dynamics-alignment-breaker.ly is obviously different as
the
Updates:
Status: Verified
Comment #6 on issue 1706 by lilyli...@googlemail.com: Beaming causes
lilypond to crash
http://code.google.com/p/lilypond/issues/detail?id=1706
In 2.15.3 there still are many error messages (identical to the one quoted
in the original post),
but Lilypond do
Updates:
Labels: fixed_2_15_4 backport
Comment #7 on issue 1643 by percival.music.ca: Part Combine problems
http://code.google.com/p/lilypond/issues/detail?id=1643
When you push something, you're claiming that it's fixed. The fixed_2_15_4
tag is an unverified claim; that claim is veri
Comment #6 on issue 1643 by pkx1...@gmail.com: Part Combine problems
http://code.google.com/p/lilypond/issues/detail?id=1643
Pushed as
8dec1b16ae6daff5b9a0f9fb806db66cf87bc5bd
James
PS once this has been verified this can be backported - I assume that the
backport flag can only (really) be
Comment #4 on issue 1714 by percival.music.ca: Build error regarding mf2pt1
with latest texlive (2011) and lilypond
http://code.google.com/p/lilypond/issues/detail?id=1714
this might be fixed in
db6910b2913115769ba736e0b0ff6a159ba4
but we're leaving it unmarked for now. The first tarba
On Tue, Jun 28, 2011 at 08:14:51AM +0200, Werner LEMBERG wrote:
> Attached is a fix which makes it work again in lilypond (without
> breaking backwards compatibility to older mpost versions), and which
> I've applied to the git repository. Please test and report whether it
> works so that we can m
Comment #8 on issue 1716 by percival.music.ca: No convert-ly rule for the
fix for issue 1655
http://code.google.com/p/lilypond/issues/detail?id=1716
Short-term fiat decision (as release meister): absolutely no
removing/renaming to syntax in a stable version, even for internal
properties.
Comment #7 on issue 1716 by pkx1...@gmail.com: No convert-ly rule for the
fix for issue 1655
http://code.google.com/p/lilypond/issues/detail?id=1716
+1 At the absolute minimum we aught to be saying
[internal function] is no longer supported and will be
[ignored/deleted/whatever] please ref
Comment #6 on issue 1716 by reinhold...@gmail.com: No convert-ly rule for
the fix for issue 1655
http://code.google.com/p/lilypond/issues/detail?id=1716
Internal properties are -- as their name already says -- internal and can
thus change without warning...
On the other hand, as a user I wo
22 matches
Mail list logo
