Pavel Roskin writes:
> I also saw this request in forum and mailing posts. They mention two
> workarounds - use \partial and hide bars or use \grace with a hidden
> note in all staves.
Grace with spacer rest possibly.
> I consider both unacceptable hacks that would affect the MIDI output and
>
Updates:
Labels: Patch-review
Comment #10 on issue 695 by lilypond...@gmail.com: slurs may take too much
vertical extent
http://code.google.com/p/lilypond/issues/detail?id=695#c10
Patchy the autobot says: LGTM.
___
bug-lilypond mailing lis
Hello!
The only thing I could not properly transcribe in Robert Schumann's "Du
bist wie eine Blume" was the key change from treble to bass in the
beginning on the right hand piano staff.
It may be a strange thing to do, but if Schumann wrote it and it was
printed in several editions of the score,
Updates:
Labels: Patch-review
Comment #1 on issue 2133 by lilypond...@gmail.com: Patch: Emacs mode lines
for parser.yy and lexer.ll
http://code.google.com/p/lilypond/issues/detail?id=2133#c1
Patchy the autobot says: LGTM.
___
bug-lilypond
Updates:
Labels: Patch-review
Comment #1 on issue 2132 by lilypond...@gmail.com: Patch: Sends woodwind
regtest op to stderr
http://code.google.com/p/lilypond/issues/detail?id=2132#c1
Patchy the autobot says: LGTM.
___
bug-lilypond mailing
Comment #24 on issue 1735 by lemniska...@gmail.com: modifying default
behaviour of tremolo slashes
http://code.google.com/p/lilypond/issues/detail?id=1735
Wow, i got a message to my other e-mail address...
2011/12/21 x.sche...@gmail.com: modifying default behaviour of tremolo
slashes
It's w
Hi,
please ignore, if this is mentioned before (I couldn't find anything about it).
Numbers in LilyPond-variables are already possible, if
superscript-numbers are used.
note⁰ = \relative c' { c1 }
note¹ = \relative c' { d1 }
note² = \relative c' { d1 }
note³ = \relative c' { f1 }
note⁴ = \relati
Comment #3 on issue 2131 by d...@gnu.org: Patch: Tie LilyPond, lexer and
parser together more type-safely.
http://code.google.com/p/lilypond/issues/detail?id=2131
Oh, and followup for replacing PARSER with parser.
c658e542fc7728e56c6bc5cd1c7c62035fac79c2
___
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2133 by d...@gnu.org: Patch: Emacs mode lines for parser.yy and
lexer.ll
http://code.google.com/p/lilypond/issues/detail?id=2133
Emacs mode lines for parser.yy and lexer.ll
http://codereview.appspot.com/5505059
__
Updates:
Status: Fixed
Owner: d...@gnu.org
Labels: -Patch-review Fixed_2_15_23
Comment #2 on issue 2131 by d...@gnu.org: Patch: Tie LilyPond, lexer and
parser together more type-safely.
http://code.google.com/p/lilypond/issues/detail?id=2131
Well, functionally it does
Updates:
Labels: Patch-new
Comment #9 on issue 695 by mts...@gmail.com: slurs may take too much
vertical extent
http://code.google.com/p/lilypond/issues/detail?id=695#c9
Give slurs skylines in outside-staff-priority calculations.
http://codereview.appspot.com/5504055
__
Comment #23 on issue 1735 by x.sche...@gmail.com: modifying default
behaviour of tremolo slashes
http://code.google.com/p/lilypond/issues/detail?id=1735
While having a look at my starred issues (and how quickly Mike fixes them)
I saw this one. I would have thought this issue was closed.
What
Status: New
Owner:
Labels: Type-Patch Patch-new
New issue 2132 by philehol...@gmail.com: Patch: Sends woodwind regtest op
to stderr
http://code.google.com/p/lilypond/issues/detail?id=2132
Sends woodwind regtest op to stderr
http://codereview.appspot.com/5502058
___
Updates:
Labels: Patch-review
Comment #8 on issue 695 by lilypond...@gmail.com: slurs may take too much
vertical extent
http://code.google.com/p/lilypond/issues/detail?id=695#c8
Patchy the autobot says: LGTM.
___
bug-lilypond mailing list
Updates:
Labels: Patch-review
Comment #1 on issue 2131 by lilypond...@gmail.com: Patch: Tie LilyPond,
lexer and parser together more type-safely.
http://code.google.com/p/lilypond/issues/detail?id=2131#c1
Patchy the autobot says: LGTM.
___
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2131 by d...@gnu.org: Patch: Tie LilyPond, lexer and parser
together more type-safely.
http://code.google.com/p/lilypond/issues/detail?id=2131
Tie LilyPond, lexer and parser together more type-safely.
Obviously, this would
Updates:
Labels: Patch-review
Comment #3 on issue 1861 by lilypond...@gmail.com: DynamicText attached to
spacer rest not correctly aligned
http://code.google.com/p/lilypond/issues/detail?id=1861#c3
Patchy the autobot says: LGTM.
___
bug-li
Updates:
Labels: Patch-new
Comment #7 on issue 695 by mts...@gmail.com: slurs may take too much
vertical extent
http://code.google.com/p/lilypond/issues/detail?id=695#c7
Give slurs skylines in outside-staff-priority calculations.
http://codereview.appspot.com/5504055
__
Updates:
Labels: Patch-review
Comment #6 on issue 695 by lilypond...@gmail.com: slurs may take too much
vertical extent
http://code.google.com/p/lilypond/issues/detail?id=695#c6
Patchy the autobot says: LGTM.
___
bug-lilypond mailing list
Updates:
Labels: Patch-review
Comment #5 on issue 257 by lilypond...@gmail.com: collision accent and
tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=257#c5
Patchy the autobot says: LGTM.
___
bug-lilypond mailing list
bug-
Updates:
Labels: Patch-review
Comment #5 on issue 2109 by lilypond...@gmail.com: do not tinker with the
position of a pitched rest
http://code.google.com/p/lilypond/issues/detail?id=2109#c5
Patchy the autobot says: LGTM.
___
bug-lilypond m
Updates:
Labels: Patch-review
Comment #4 on issue 2094 by lilypond...@gmail.com:
spacing-measure-length.ly regtest has time sig overlaying rest
http://code.google.com/p/lilypond/issues/detail?id=2094#c4
Patchy the autobot says: LGTM.
___
b
Updates:
Labels: Patch-new
Comment #2 on issue 1861 by mts...@gmail.com: DynamicText attached to
spacer rest not correctly aligned
http://code.google.com/p/lilypond/issues/detail?id=1861#c2
Correctly centers dynamics in the Dynamics context.
http://codereview.appspot.com/5498058
__
lilypond-4 wrote:
>
>
>
and i forgot to tell that
--include, -I=directory
should be
-I, --include=directory
thanks!
--
View this message in context:
http://old.nabble.com/Issue-2111-in-lilypond%3A-documentation-of-include-settings-in-Usage-tp32989659p33017184.html
Sent from the Gnu -
Updates:
Labels: Patch-new
Comment #5 on issue 695 by mts...@gmail.com: slurs may take too much
vertical extent
http://code.google.com/p/lilypond/issues/detail?id=695#c5
Give slurs skylines in outside-staff-priority calculations.
http://codereview.appspot.com/5504055
__
Comment #2 on issue 2111 by elu...@gmail.com: documentation of
include-settings in Usage
http://code.google.com/p/lilypond/issues/detail?id=2111
i'd go for 3.
suggestions:
AU: Command line options for lilypond
The following options are supported:
(it's not sorted in version 2.15.22)
Updates:
Labels: -Type-Defect -Priority-Low Type-Ugly
Comment #4 on issue 695 by pkx1...@gmail.com: slurs may take too much
vertical extent
http://code.google.com/p/lilypond/issues/detail?id=695
Taken from a message on user with a workaround in this specific case that
may help other
Updates:
Labels: -Patch-needs_work Patch-new
Comment #4 on issue 2109 by benko@gmail.com: do not tinker with the
position of a pitched rest
http://code.google.com/p/lilypond/issues/detail?id=2109
(No comment was entered for this change.)
_
Comment #3 on issue 2109 by benko@gmail.com: do not tinker with the
position of a pitched rest
http://code.google.com/p/lilypond/issues/detail?id=2109
patch updated
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailm
Updates:
Labels: Patch-new
Comment #4 on issue 257 by mts...@gmail.com: collision accent and tuplet
bracket
http://code.google.com/p/lilypond/issues/detail?id=257#c4
Avoids Script TupletBracket collisions by default
http://codereview.appspot.com/5505055
Updates:
Status: Fixed
Comment #5 on issue 2123 by mts...@gmail.com: Patch: Gets cross-staff
collisions right for beams.
http://code.google.com/p/lilypond/issues/detail?id=2123
Pushed to staging as d82eb992f3c17c42b9d01861d2c90d551d155620.
__
Updates:
Status: Fixed
Comment #7 on issue 2122 by mts...@gmail.com: Regression in
chord-name-exceptions.ly - badly spaced chord names
http://code.google.com/p/lilypond/issues/detail?id=2122
Pushed to staging as aa6e1d76a80115776ed0a7fb82368681dfc5ffed.
_
Updates:
Status: Fixed
Comment #5 on issue 2116 by mts...@gmail.com: Patch: Shows Flags in
tabFullNotation
http://code.google.com/p/lilypond/issues/detail?id=2116
Pushed to staging as c7e244eee50f301ace3954f593657eb6d145dd52.
___
bug-lilyp
33 matches
Mail list logo
