Updates:
Status: Verified
Comment #4 on issue 1769 by philehol...@googlemail.com: Doc: Usage 5.5,
wrong file name in snippet
http://code.google.com/p/lilypond/issues/detail?id=1769
(No comment was entered for this change.)
___
Updates:
Status: Verified
Comment #9 on issue 1728 by philehol...@googlemail.com: Implements
multi-line non-cross staff glissandi
http://code.google.com/p/lilypond/issues/detail?id=1728
(No comment was entered for this change.)
___
Updates:
Labels: verified_2_15_5
Comment #21 on issue 75 by philehol...@googlemail.com: Slurs cannot be
nested (including acciaccatura and appoggiatura)
http://code.google.com/p/lilypond/issues/detail?id=75
(No comment was entered for this change.)
Attachments:
SlurApp.png
Updates:
Labels: -Patch-needs_work Patch-review
Comment #22 on issue 1752 by lemniska...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
clef selection for non-G clefs if 'old style is set is fixed now.
Updates:
Labels: -Patch-needs_work Patch-new
Comment #9 on issue 1214 by reinhold...@gmail.com: Cue notes to music that
creates a sub-voice does not work
http://code.google.com/p/lilypond/issues/detail?id=1214
New patch is up that fixes quote-cyclic.ly (or rather it fixes quoting
Updates:
Labels: -Patch-needs_work Patch-review
Comment #8 on issue 1735 by lemniska...@gmail.com: modifying default
behaviour of tremolo slashes
http://code.google.com/p/lilypond/issues/detail?id=1735
New patch set uploaded, now with current Lily behaviour as the default.
Status: New
Owner:
Labels: Type-Documentation Frog
New issue 1775 by lemniska...@gmail.com: doc: add broken- and unbroken slur
shaping function
http://code.google.com/p/lilypond/issues/detail?id=1775
Add the shapeSlur function, mentioned here and there:
On 20 July 2011 15:26, Neil Puttock n.putt...@gmail.com wrote:
Let me think about it for a bit. I have an idea using a scheme
engraver which might work.
Here's the scheme engraver if you want to try it out. It's obviously
not as sophisticated as Mike's proposed fix, but it does have the
Comment #4 on issue 307 by mts...@gmail.com: collision slur with tuplet
bracket
http://code.google.com/p/lilypond/issues/detail?id=307
What would be the ideal output in this case? Should the tuplet bracket and
number be moved up, should the slur end higher, or should the tuplet
bracket
Status: New
Owner:
Labels: Type-Documentation Priority-High Frog
New issue 1776 by lemniska...@gmail.com: doc: \compoundMeter isn't
documented
http://code.google.com/p/lilypond/issues/detail?id=1776
a function for compound meter was added to 2.14, but the docs still show an
old way of
Comment #9 on issue 1735 by x.sche...@gmail.com: modifying default
behaviour of tremolo slashes
http://code.google.com/p/lilypond/issues/detail?id=1735
Thanks a lot!
BTW I did not meant to *impose* current settings as default, but rather
ask for opening a wider discussion when changing such
Comment #10 on issue 1735 by lemniska...@gmail.com: modifying default
behaviour of tremolo slashes
http://code.google.com/p/lilypond/issues/detail?id=1735
Xavier,
i understand. However, i'm currently busy with closing several opened
issues and some other Lily-related things, so i don't
Updates:
Labels: Patch-new
Comment #11 on issue 163 by pkx1...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
From Mike:
--snip--
Message:
Hey all,
This fixes issue 163. The only downside is that it adds another entry
Status: Accepted
Owner: n.putt...@gmail.com
Labels: Type-Documentation Priority-Medium Patch-new
New issue 1777 by pkx1...@gmail.com: adds auto-generated documentation for
context modifications
http://code.google.com/p/lilypond/issues/detail?id=1777
This patch adds auto-generated
Status: Accepted
Owner:
Labels: Type-Documentation Priority-Medium
New issue 1778 by pkx1...@gmail.com: slashedGrace function (graces with
slashed stems but no slur, e.g. when grace is tied) needs documenting
http://code.google.com/p/lilypond/issues/detail?id=1778
Comment from Mark
Updates:
Owner: mts...@gmail.com
Labels: Patch-new
Comment #4 on issue 36 by pkx1...@gmail.com: collision cresc and kneed beams
http://code.google.com/p/lilypond/issues/detail?id=36
From Mike:
--snip--
Message:
I think that this is sufficient to fix issue 36. As Graham points
Comment #11 on issue 1735 by pkx1...@gmail.com: modifying default behaviour
of tremolo slashes
http://code.google.com/p/lilypond/issues/detail?id=1735
Is this jus a new-look or 'slightly altered' tremelo patch?
Comment #23 on issue 1752 by carl.d.s...@gmail.com: redesigning G clef in
our Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
It seems to me that we do not have agreement for having an override for the
clef. As far as I can see, there are those who prefer the old clef,
On 19 June 2011 16:36, Reinhold Kainhofer reinh...@kainhofer.com wrote:
Is there any current way to switch on/off expansion of the repeats in both
scores for the midi output, other than manually prepending \unfoldRepeats in
BOTH scores?
I had a look at this when issue #769 was created. There
Hello,
From: bug-lilypond-bounces+james.lowe=datacore@gnu.org
[bug-lilypond-bounces+james.lowe=datacore@gnu.org] on behalf of
lilyp...@googlecode.com [lilyp...@googlecode.com]
Sent: 23 July 2011 23:38
To: bug-lilypond@gnu.org
Subject: Re: Issue
Comment #24 on issue 1752 by n.putt...@gmail.com: redesigning G clef in our
Feta font
http://code.google.com/p/lilypond/issues/detail?id=1752
I am *not* in favor of including the clef style override in lilypond --
it's a hack
that is not extensible and not maintainable in the long term.
Carl wrote
I am *not* in favor of including the clef style override in
lilypond -- it's a hack that is not extensible and not
maintainable in the long term.
Neither is Han-Wen. See comment 17:
I vote against overrides; we have too many of them, and the
difference between the old and new
Updates:
Summary: Semi-breves unnecessarily shifted
Comment #1 on issue 1774 by k-ohara5...@oco.net: Semi-breves unnecessarily
shifted
http://code.google.com/p/lilypond/issues/detail?id=1774
Maybe desired behavior would be let the inner voices (those with
\shiftOn...) ignore outer
Comment #5 on issue 307 by lemzw...@googlemail.com: collision slur with
tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=307
For my test case, I suggest to position the `more local' context next to
the staff. Thus I would like to have the tuple bracket unchanged, and the
24 matches
Mail list logo
