Updates:
Status: Verified
Comment #8 on issue 1518 by brownian.box: DOC: add explanation of part
combine functions
http://code.google.com/p/lilypond/issues/detail?id=1518
The patch is really pushed --i can see the docs changes ,)
___
bug-l
Comment #7 on issue 1530 by brownian.box: [PATCH] Fret diagram fixes (Issue
4176056)
http://code.google.com/p/lilypond/issues/detail?id=1530
I can't verify this, sorry. Regtest is compiled, i can see that, but i
can't be sure that it shows correct picture.
___
On Sat 26 Mar 2011, 20:45 Michael Welsh Duggan wrote:
> When including a small descant lyric line, an extender at the end may
> end up extending indefinitely. I am working from git as of yesterday:
>
> \version "2.13.51"
>
> <<
> \new Lyrics = above \with {
> \override VerticalAxisGroup #
Status: Accepted
Owner:
Labels: Type-Defect Priority-Medium
New issue 1579 by brownian.box: Overextended lyrics extenders
http://code.google.com/p/lilypond/issues/detail?id=1579
Reported by Michael Welsh Duggan,
http://lists.gnu.org/archive/html/bug-lilypond/2011-03/msg00459.html :
% the
Status: Accepted
Owner:
Labels: Type-Enhancement Priority-Medium Patch-review
New issue 1578 by colinpkc...@gmail.com: Enhancement: Allows glissandi to
be continuous at line breaks
http://code.google.com/p/lilypond/issues/detail?id=1578
Mike Solomon has proposed an enhancement to the gli
On 3/27/11 7:37 AM, "Trevor Daniels" wrote:
>
>
> Frédéric Bron wrote Sunday, March 27, 2011 7:55 AM
>
>
>> I have built an exhaustive example showing the placement of all
>> objects. Maybe you could include it in lieu of the one that is
>> already
>> given and that has only a few of them.
Here's a slightly different example of this problem (different
scenario).
<<
\new Staff \new Voice = "main" { a2 a( a) a^"No lyrics" a a( a) a }
\new Lyrics \lyricsto "main" \lyricmode {
aa, aa, __ \skip 1 \skip 1 aa, __ aa. }
>>
Here the extender extends through the skipped section.
-
Reinhold Kainhofer writes:
> On So., 27. Mär. 2011 18:23:16 CEST, Phil Holmes wrote:
>
>> "Michael Welsh Duggan" wrote in message
>> news:87pqpdtmqx@maru.md5i.com...
>> > When including a small descant lyric line, an extender at the end may
>> > end up extending indefinitely. I am workin
On So., 27. Mär. 2011 18:23:16 CEST, Phil Holmes wrote:
> "Michael Welsh Duggan" wrote in message
> news:87pqpdtmqx@maru.md5i.com...
> > When including a small descant lyric line, an extender at the end may
> > end up extending indefinitely. I am working
> I think this is because you ha
"-Eluze" wrote in message
news:31250925.p...@talk.nabble.com...
Michael Welsh Duggan-4 wrote:
When including a small descant lyric line, an extender at the end may
end up extending indefinitely.
with version 2.13.18 this seems ok but starting with 2.13.19 this strange
behaviour shows up!
hello
On 27 Mar 2011, at 14:37, "Trevor Daniels" wrote:
> It could go in the Notation Reference with some introductory
> text, but I prefer Phil's suggestion to include this in the
> regression test suite.
Yes I think this could go as a reg test. It might be nice as an Appendix to the
NR but
"Michael Welsh Duggan" wrote in message
news:87pqpdtmqx@maru.md5i.com...
When including a small descant lyric line, an extender at the end may
end up extending indefinitely. I am working from git as of yesterday:
-
>> Could this lead to undefined behavior? i.e. sometimes have TextScript
>> above MultiMeasureRestText and sometimes the contrary?
>
> Yes. I believe in this case it depends on the order
> in which they appear in the .ly file.
> What order would you like?
I have tried to inverse the order in the
Comment #11 on issue 76 by pkx1...@gmail.com: beams should not collide with
accidentals
http://code.google.com/p/lilypond/issues/detail?id=76
an @knownissue has been added at the behest of mike S where use a similar
example. in this case manual beaming stops the collisions.
http://git.sav
Michael Welsh Duggan-4 wrote:
>
> When including a small descant lyric line, an extender at the end may
> end up extending indefinitely.
>
with version 2.13.18 this seems ok but starting with 2.13.19 this strange
behaviour shows up!
--
View this message in context:
http://old.nabble.com/Ove
Frédéric Bron wrote Sunday, March 27, 2011 3:49 PM
I have a remaining question: why have TextScript and
MultiMeasureRestText the same outside-staff-priority (450)?
A good question (meaning I don't know the answer :)
It could be that whoever chose the values couldn't decide
which should be hi
> It could go in the Notation Reference with some introductory
> text, but I prefer Phil's suggestion to include this in the
> regression test suite.
>
> However we choose to use it, many thanks for the contribution!
You are welcome.
I have a remaining question: why have TextScript and
MultiMeasu
Frédéric Bron wrote Sunday, March 27, 2011 7:55 AM
I have built an exhaustive example showing the placement of all
objects. Maybe you could include it in lieu of the one that is
already
given and that has only a few of them. This could help
understanding
for example what is a multimeasure r
Comment #10 on issue 76 by philehol...@googlemail.com: beams should not
collide with accidentals
http://code.google.com/p/lilypond/issues/detail?id=76
The collision still occurs using 2.13.55, which fixes issue 37.
___
bug-lilypond mailing list
bu
Updates:
Status: Fixed
Labels: -fixed
Comment #18 on issue 37 by philehol...@googlemail.com: collision notehead
and beams
http://code.google.com/p/lilypond/issues/detail?id=37
(No comment was entered for this change.)
___
bug-lilyp
Updates:
Labels: -Patch-needs_work fixed
Comment #17 on issue 37 by philehol...@googlemail.com: collision notehead
and beams
http://code.google.com/p/lilypond/issues/detail?id=37
(No comment was entered for this change.)
___
bug-lilypond m
Updates:
Labels: fixed_2_13_55
Comment #16 on issue 37 by philehol...@googlemail.com: collision notehead
and beams
http://code.google.com/p/lilypond/issues/detail?id=37
Confirmed fixed in 13.55.
___
bug-lilypond mailing list
bug-lilypond@g
I think it could be worth including this as a regtest?
Phil Holmes
Bug Squad
"Frédéric Bron" wrote in message
news:AANLkTinkvD-LVYS4YNvSDN1Hj2-Su5Zpd8vQruVrGyP=@mail.gmail.com...
I've just made a more extensive change to the LM so it accords with the
new
behaviour in 2.13.
Thanks for answ
23 matches
Mail list logo
