2011/4/14 James Lowe :
> I use Lilygit.tcl every single day. I've just used it this morning - I can't
> produce patches without it.
> I have to admit that I have not had to use lilygit to pull a brand new
> install for a few weeks, but nothing has been added to Lilygit.tcl for a lot
> longer tha
Comment #3 on issue 1609 by k-ohara5...@oco.net: unpredictable change of
voicing
http://code.google.com/p/lilypond/issues/detail?id=1609
The troublesome regtest, midi/partcombine.ly, sets two voices in
\partcombine, which produces four voices in the midi output, each on their
own track :
Comment #2 on issue 1609 by k-ohara5...@oco.net: unpredictable change of
voicing
http://code.google.com/p/lilypond/issues/detail?id=1609
The troublesome regtest, midi/partcombine.ly, sets two voices in
\partcombine, which produces four voices in the midi output, each on their
own track :
Comment #1 on issue 1609 by k-ohara5...@oco.net: unpredictable change of
voicing
http://code.google.com/p/lilypond/issues/detail?id=1609
The completion- engravers are not essential, it is simply the fact that
LilyPond does not have a rule to place simultaneous rests with a note of
differe
Updates:
Labels: -Patch-needs_work Patch-review
Comment #2 on issue 1582 by colinpkc...@gmail.com: flag variants patch
http://code.google.com/p/lilypond/issues/detail?id=1582
(No comment was entered for this change.)
___
bug-lilypond mailing
Hi Graham,
On 15/04/11 11:17, Graham Percival wrote:
> On Thu, Apr 14, 2011 at 09:43:51PM +0100, Ian Hulin wrote:
>> `/home/ian/lilypond/build/Documentation/out-www/essay/literature.texi'...
>> Processing include: colorado.itexi
>> lilypond-book.py: error: file not found: colorado.itexi
>
> Do yo
Comment #12 on issue 1612 by k-ohara5...@oco.net: Change staff produces
long stems
http://code.google.com/p/lilypond/issues/detail?id=1612
Switching off beam-collision-prevention for cross-staff beams seems very
sensible.
Generally, collision-prevention is turned off for cross-staff graph
On Fri, Apr 15, 2011 at 11:19:12AM -0600, Carl Sorensen wrote:
> On 4/15/11 9:23 AM, "Graham Percival" wrote:
>
> > Great! I'll make another unstable release tomorrow and merge it
> > into stable/2.14, and thereafter you can cherry-pick at will.
> > I'll make all future 2.13 releases from stable
Updates:
Labels: -Priority-Postponed Priority-Medium
Comment #5 on issue 630 by philehol...@googlemail.com: non-synchronized
grace note makes voiceOne go stems down
http://code.google.com/p/lilypond/issues/detail?id=630
There's a similar problem when the grace note follows \oneVoice i
Comment #3 on issue 1613 by bordage@gmail.com: Beamed stems too long
when avoiding low note in other voice
http://code.google.com/p/lilypond/issues/detail?id=1613
Han-Wen's commit has broken Beam_collision_engraver. One example among
others :
\relative c'' { d32 ees d c b c b a }
Att
Comment #11 on issue 1612 by hanw...@gmail.com: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
maybe we should just switch off beam collisions for x-staff beams.
___
bug-lilypond mailing list
bug-lilypond@
Comment #10 on issue 1612 by hanw...@gmail.com: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
actually, we may have to ponder a bit more how to do collisions. I think
manual changes may also be fubar'd when the voice changes mid-beam, and the
ot
On Fri, Apr 15, 2011 at 7:30 AM, m...@apollinemike.com
wrote:
>>> OK. http://code.google.com/p/lilypond/issues/detail?id=1613
>>
>> I am testing a fix for this; it was an oversight of mine.
>>
>> Graham,
>>
>> this issue was exposed due to a (seemingly innocuous) one-line change
>> by Mike. Can
Comment #9 on issue 1612 by percival.music.ca: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
Do I understand correctly that lilypond can no longer handle staff changes
with automatic beaming?
If so, then I think this should be noted in the change
Comment #8 on issue 1612 by pkx1...@gmail.com: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
@knownissue added for acceptance/rejection
http://codereview.appspot.com/4440041/
___
bug-lilypond mailing lis
On Apr 14, 2011, at 11:08 PM, Han-Wen Nienhuys wrote:
> On Thu, Apr 14, 2011 at 9:00 AM, Phil Holmes wrote:
could argue that lengthening a stem to avoid a collision that isn't a
collision is a bug, but I wouldn't do so without Mike's input.
>>>
>>> Hm? A bug with an explanation and a
Comment #7 on issue 1612 by m...@apollinemike.com: Change staff produces
long stems
http://code.google.com/p/lilypond/issues/detail?id=1612
I propose, then, that we downgrade this to `high' with a @knownissues in
the docs suggesting manual beams and a NOT_SMART convert-ly rule telling
peo
Comment #2 on issue 1613 by m...@apollinemike.com: Beamed stems too long
when avoiding low note in other voice
http://code.google.com/p/lilypond/issues/detail?id=1613
The original snippet, posted by Friedrich Fischer, still produces bad
output:
\version "2.13.59"
\new Staff {
\time 6/8
\k
On Thu, Apr 14, 2011 at 09:43:51PM +0100, Ian Hulin wrote:
> `/home/ian/lilypond/build/Documentation/out-www/essay/literature.texi'...
> Processing include: colorado.itexi
> lilypond-book.py: error: file not found: colorado.itexi
Do you have bibtex installed? (are you using lilydev or your own
sy
On Thu, Apr 14, 2011 at 11:23:56AM +0200, Janek Warchoł wrote:
> |git --git-dir=/home/janek/lilypond-git/.git fetch --depth 1 2>@1
> )
> But then nothing happens.
Confirmed. :(
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=1615
Could somebody look into this? It's a serio
Status: Accepted
Owner:
Labels: Type-Other Priority-High Maintainability
New 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
Savannah isn't responding to
git fetch --depth 1
T
Updates:
Status: Fixed
Comment #2 on issue 1614 by philehol...@googlemail.com: DynamicTextSpanner
documentation is wrong
http://code.google.com/p/lilypond/issues/detail?id=1614
(No comment was entered for this change.)
___
bug-lilypond mai
"Olexa Bilaniuk" wrote in message
news:loom.20110415t051733-...@post.gmane.org...
I'm not top posting.
While trying to create a custom crescendo in LilyPond 2.13.59 and 2.12.3,
I came
up against what I believe is a bug in DynamicTextSpanner's style override
: When
I set 'style to 'hairpin, w
Comment #1 on issue 1614 by philehol...@googlemail.com: DynamicTextSpanner
documentation is wrong
http://code.google.com/p/lilypond/issues/detail?id=1614
I think this is simply a bug in the snippet. AFAICS the default for a text
spanner is a dashed line. I've added this as an issue to get
Status: Accepted
Owner:
Labels: Type-Documentation Priority-Medium
New issue 1614 by philehol...@googlemail.com: DynamicTextSpanner
documentation is wrong
http://code.google.com/p/lilypond/issues/detail?id=1614
From Olexa Bilaniuk:
While trying to create a custom crescendo in LilyPond 2
Colin Campbell wrote Friday, April 15, 2011 4:18 AM
On 11-04-14 04:12 PM, Trevor Daniels wrote:
Mark Polesky wrote Thursday, April 14, 2011 10:02 PM
I just found a problem with an old doc-commit of mine
(0a8cfef, from May 7 2010). I implicitly endorsed using
barchecks in the lyrics input
\relative c'' {
\override Voice.Script #'staff-padding = #'() % only necessary for 2.13.10
\stemUp
c4 ~ c4->
}
produces different output with 2.13.9 and 2.13.10 (or higher)
noteable is the collision with the accent.
http://old.nabble.com/file/p31403595/2.13.9.preview.png
http://old.nabb
27 matches
Mail list logo
