bruys . noten...@gmail.com wrote in message
news:banlktinz8-p51gg01wpxsn3a2zt8vn+...@mail.gmail.com...
*The current situation*
http://code.google.com/p/lilypond/issues/detail?id=1631
--
Phil Holmes
Bug Squad
___
bug-lilypond mailing list
Status: Accepted
Owner:
Labels: Type-Enhancement Priority-Medium
New issue 1631 by philehol...@googlemail.com: Feature request: Tuplet
bracket style settings
http://code.google.com/p/lilypond/issues/detail?id=1631
Requested by Bruys:
*The current situation*
a) Lilypond's default
Comment #1 on issue 1631 by v.villen...@gmail.com: Feature request: Tuplet
bracket style settings
http://code.google.com/p/lilypond/issues/detail?id=1631
Another feature that could be added to LilyPond wrt tuplet printing, is
that in many printed scores, tuplets are not indicated with a
Updates:
Labels: -Patch-review Patch-new
Comment #15 on issue 1612 by percival.music.ca: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
New patches from Mike here:
http://codereview.appspot.com/4423062/
http://codereview.appspot.com/4431058/
Updates:
Labels: -Patch-new Patch-review
Comment #16 on issue 1612 by percival.music.ca: Change staff produces long
stems
http://code.google.com/p/lilypond/issues/detail?id=1612
Clean regtests,
___
bug-lilypond mailing list
Comment #1 on issue 1618 by percival.music.ca: unpredictable placement of
rests
http://code.google.com/p/lilypond/issues/detail?id=1618
I think it happened earlier than 2.13.48 -- maybe even before 2.12 or 2.10,
meaning that it's not Critical. I tried to do a bisect, but I ended up
You can run valgrind on lilypond. You just need to disable the
warnings regarding garbage collection.
On Sun, Apr 17, 2011 at 5:24 AM, lilyp...@googlecode.com wrote:
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical
New issue 1618 by percival.music.ca: unpredictable
On Thu, Apr 21, 2011 at 3:49 PM, Trevor Daniels t.dani...@treda.co.ukwrote:
One or two quibbles with the language on this page:
I'll fix the typos.
Thanks, Trevor! Someone must have clumsy typing ... oops!
___
bug-lilypond mailing list
Updates:
Labels: -Priority-Critical Priority-High
Comment #2 on issue 1618 by k-ohara5...@oco.net: unpredictable placement of
rests
http://code.google.com/p/lilypond/issues/detail?id=1618
Quite possibly the problem existed in 2.13.48, and my testing missed it.
Testing for
Comment #1 on issue 1547 by k-ohara5...@oco.net: Too many colliding resrts
http://code.google.com/p/lilypond/issues/detail?id=1547
Pitched rests {\voiceFour a'8 b'\rest} can produce good output but still
issue the warning.
Better behavior would be to suppress the warning if the too many
Updates:
Labels: Patch-review
Comment #6 on issue 1613 by hanw...@gmail.com: Beamed stems too long when
avoiding low note in other voice
http://code.google.com/p/lilypond/issues/detail?id=1613
http://codereview.appspot.com/4450052
regtest looks clean.
Comment #17 on issue 1612 by n.putt...@gmail.com: Change staff produces
long stems
http://code.google.com/p/lilypond/issues/detail?id=1612
Unfortunately, Mike's patch doesn't fix these cases (they're probably a
related, but separate bug):
\new Staff = up \relative c' {
c8 c c c
Since yesterday, make doc is erroring on a segfault from
Documentation/web/ly-examples/bach-schenker.ly although the .ly compiles
fine if I load it into Frescobaldi. If anyone else is having the
problem, I'll raise an issue. I deleted ~/lilypond-git then git init
and git clone, then
13 matches
Mail list logo
