Updates:
Labels: Patch-new
Comment #8 on issue 460 by mts...@gmail.com: bar numbers for broken bars
http://code.google.com/p/lilypond/issues/detail?id=460#c8
Adds parenthesized measure numbers at mid-bar breaks.
http://codereview.appspot.com/5452057
___
Updates:
Status: Invalid
Comment #4 on issue 2073 by mts...@gmail.com: Patch: Allows for framing
comments in LilyPond backends.
http://code.google.com/p/lilypond/issues/detail?id=2073
(No comment was entered for this change.)
___
bug-lilyp
Updates:
Status: Fixed
Labels: -Fixed_2_5_21 Fixed_2_5_22
Comment #18 on issue 2067 by d...@gnu.org: Patch: Give \displayLilyMusic
and \displayMusic optional port arguments.
http://code.google.com/p/lilypond/issues/detail?id=2067
Had to rebase staging. Now pushed as
a9829dd
Updates:
Labels: -Patch-push Fixed_2_5_21
Comment #17 on issue 2067 by d...@gnu.org: Patch: Give \displayLilyMusic
and \displayMusic optional port arguments.
http://code.google.com/p/lilypond/issues/detail?id=2067
Pushed 656d877af5b504967d38399fae7431a94a35c738 to staging. This still
Updates:
Labels: Patch-review
Comment #2 on issue 2080 by lilypond...@gmail.com: Request for better cross
referencing of ornaments
http://code.google.com/p/lilypond/issues/detail?id=2080#c2
Patchy the autobot says: LGTM.
___
bug-lilypond m
Updates:
Labels: Patch-review
Comment #10 on issue 409 by lilypond...@gmail.com: Using whiteout and layer
properties for ties avoiding collision with staff objects
http://code.google.com/p/lilypond/issues/detail?id=409#c10
Patchy the autobot says: LGTM.
_
Updates:
Labels: Patch-needs_work
Comment #7 on issue 460 by lilypond...@gmail.com: bar numbers for broken
bars
http://code.google.com/p/lilypond/issues/detail?id=460#c7
Patchy the autobot says: patch does not apply
___
bug-lilypond mailin
Updates:
Labels: -Patch-countdown Patch-push
Comment #7 on issue 2069 by colinpkc...@gmail.com: Patch: More nuanced
BarLine extra-spacing-height to allow tighter horizontal spacing
http://code.google.com/p/lilypond/issues/detail?id=2069
Counted down to 20111206
Updates:
Labels: -Patch-countdown Patch-push
Comment #16 on issue 2067 by colinpkc...@gmail.com: Patch: Give
\displayLilyMusic and \displayMusic optional port arguments.
http://code.google.com/p/lilypond/issues/detail?id=2067
Counted down to 20111206
Status: Accepted
Owner: mts...@gmail.com
Labels: Type-Critical Regression
New issue 2083 by mts...@gmail.com: \break in alternative causes score to
split
http://code.google.com/p/lilypond/issues/detail?id=2083
Works in 2.14.0, broken in current master
\relative c' {
\repeat volta 4 {
c
Updates:
Status: Fixed
Labels: -Patch-countdown Fixed_2_15_21
Comment #5 on issue 2036 by d...@gnu.org: make test in flower subdirectory
produces lots of warnings with g++ 4.6
http://code.google.com/p/lilypond/issues/detail?id=2036
Does not really need the red tape I guess. P
Comment #14 on issue 2059 by x.sche...@gmail.com: Bar numbering of
alternatives
http://code.google.com/p/lilypond/issues/detail?id=2059
The use of this
\set Score.alternativeNumberingStyle = #'number
or
\set Score.alternativeNumberingStyle = #'numbers-with-letters
deserves an explanat
Comment #7 on issue 2076 by d...@gnu.org: Doc: improve NR 1.6.3 Instrument
names (better to use \with )
http://code.google.com/p/lilypond/issues/detail?id=2076
I agree with Xavier.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.g
Comment #6 on issue 460 by mts...@gmail.com: bar numbers for broken bars
http://code.google.com/p/lilypond/issues/detail?id=460
I'm not sure if it's standard practice either...
The easiest way for me to do this would be to figure out all of the
different options and then roll them into one fu
2011/12/6 Werner :
> Hallo.
>
> Die vierte Unterüberschrift unter 1.6.3. „Stichnoten“ finde ich irritierend.
> Es geht hier wirklich nur um eine Form von „Stichnoten“ - nämlich
> abschnittsweise Zitate anderer Stimmen. Diese haben zunächst nicht einmal
> kleinere Noten, was ich bei Stichnoten imme
Comment #5 on issue 460 by x.sche...@gmail.com: bar numbers for broken bars
http://code.google.com/p/lilypond/issues/detail?id=460
Could it be possible (as an option) to print it in parentheses but
also in italic?
I do not know if this is "standard practice" but IIRC I have seen it
this way som
Comment #6 on issue 2076 by x.sche...@gmail.com: Doc: improve NR 1.6.3
Instrument names (better to use \with )
http://code.google.com/p/lilypond/issues/detail?id=2076
If you change the instrument name in the middle of the piece, then you
must use the \set Staff.shortInstrumentName = #"two"
Updates:
Summary: Using whiteout and layer properties for ties avoiding collision
with staff objects
Status: Started
Owner: pkx1...@gmail.com
Labels: Patch-new
Comment #8 on issue 409 by pkx1...@gmail.com: Using whiteout and layer
properties for ties avoiding collisi
Updates:
Status: Fixed
Comment #4 on issue 1874 by mts...@gmail.com: some stems are no longer
transparent in the docs
http://code.google.com/p/lilypond/issues/detail?id=1874
Sorry, this should no longer be an issue. I'm marking it as fixed.
Cheers,
MS
_
Comment #10 on issue 1269 by pkx1...@gmail.com: Doc: using
#'non-break-align-symbols = #'() to align MetronomeMark should be documented
http://code.google.com/p/lilypond/issues/detail?id=1269
Nothing updated on this for a year. I think (or did think when I put in the
last comment) that this
Updates:
Owner: mts...@gmail.com
Comment #3 on issue 1874 by pkx1...@gmail.com: some stems are no longer
transparent in the docs
http://code.google.com/p/lilypond/issues/detail?id=1874
Mike is this issue still relevant?
James
___
bug-lily
Updates:
Owner: pkx1...@gmail.com
Labels: Patch-new
Comment #1 on issue 2080 by pkx1...@gmail.com: Request for better cross
referencing of ornaments
http://code.google.com/p/lilypond/issues/detail?id=2080
Patch uploaded at
http://codereview.appspot.com/5452059
___
Comment #5 on issue 2076 by pkx1...@gmail.com: Doc: improve NR 1.6.3
Instrument names (better to use \with )
http://code.google.com/p/lilypond/issues/detail?id=2076
David,
Thanks. with regard to the second example:
--snip--
@lilypond[verbatim,quote,ragged-right,relative=1]
\set Staff.instru
Comment #4 on issue 460 by mts...@gmail.com: bar numbers for broken bars
http://code.google.com/p/lilypond/issues/detail?id=460#c4
Adds parenthesized measure numbers at mid-bar breaks.
http://codereview.appspot.com/5452057
___
bug-lilypond mailing l
Hallo.
Die vierte Unterüberschrift unter 1.6.3. „Stichnoten“ finde ich irritierend.
Es geht hier wirklich nur um eine Form von „Stichnoten“ - nämlich
abschnittsweise Zitate anderer Stimmen. Diese haben zunächst nicht einmal
kleinere Noten, was ich bei Stichnoten immer erwarten würde.
Dazu komm
Updates:
Status: Fixed
Labels: -Patch-push
Comment #21 on issue 1875 by d...@gnu.org: tests for flower appear to miss
instantiations of classes
http://code.google.com/p/lilypond/issues/detail?id=1875
Pushed as a4fb364a0058f701e4e25e799b5ddef511effd72 if I haven't gotten all
Comment #4 on issue 2076 by d...@gnu.org: Doc: improve NR 1.6.3 Instrument
names (better to use \with )
http://code.google.com/p/lilypond/issues/detail?id=2076
Huh?!?!
You are wildly mixing the context mod and the music.
<<
\new Staff \with { instrumentName = "Flute" }
{
f2 g4 f
}
Comment #3 on issue 2076 by pkx1...@gmail.com: Doc: improve NR 1.6.3
Instrument names (better to use \with )
http://code.google.com/p/lilypond/issues/detail?id=2076
David,
Thanks, while the first two examples in this specific section are trivial
to change the next two are not:
--snip--
Updates:
Status: Started
Cc: pkx1...@gmail.com
Comment #1 on issue 2040 by pkx1...@gmail.com: Documentation for
unpure-pure-containers
http://code.google.com/p/lilypond/issues/detail?id=2040
(No comment was entered for this change.)
__
Updates:
Labels: Patch-new
Comment #3 on issue 460 by mts...@gmail.com: bar numbers for broken bars
http://code.google.com/p/lilypond/issues/detail?id=460#c3
Adds parenthesized measure numbers at mid-bar breaks.
http://codereview.appspot.com/5452057
___
Updates:
Status: Fixed
Labels: -Patch-review
Comment #2 on issue 2081 by d...@gnu.org: Patch: Remove spurious spaces
from music expression display, adapt tests.
http://code.google.com/p/lilypond/issues/detail?id=2081
Pushed to staging as 36bb5b7742c569408e4565fe0c3c01756b6486b
Comment #2 on issue 2076 by d...@gnu.org: Doc: improve NR 1.6.3 Instrument
names (better to use \with )
http://code.google.com/p/lilypond/issues/detail?id=2076
Hi James, you said you started. Here is a bit more information:
When do you want to use a context modification, and when a normal
Updates:
Status: Started
Owner: pkx1...@gmail.com
Comment #1 on issue 2076 by pkx1...@gmail.com: Doc: improve NR 1.6.3
Instrument names (better to use \with )
http://code.google.com/p/lilypond/issues/detail?id=2076
(No comment was entered for this change.)
__
Comment #3 on issue 2082 by gra...@percival-music.ca: patchy should check
for guile memory leaks
http://code.google.com/p/lilypond/issues/detail?id=2082
yes, so evidently we'd need an
--enable-guile-memory-check
flag for configure, which would set a flag in the build system,
which would add
lilyp...@googlecode.com writes:
> Status: Accepted
> Owner:
> Labels: Type-Maintainability
>
> New issue 2082 by gra...@percival-music.ca: patchy should check for
> guile memory leaks
> http://code.google.com/p/lilypond/issues/detail?id=2082
>
> apparently there's some way to check for memory
Comment #4 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
Actually, as I move the patch to behave more like Lilypond works by default
(only keeping articulations in "articulations" inside
36 matches
Mail list logo
