Updates:
Status: Duplicate
Mergedinto: 2300
Comment #22 on issue 2109 by janek.li...@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 #21 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
I messed up the uploading, so it's the same Rietveld issue but a new
tracker issue:
http://code.google.com/p/lilypond/issues/detail?id
Comment #20 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
shall I open a new rietveld issue for the new patch or use the old one?
http://codereview.appspot.com/5434061/
Updates:
Status: Started
Comment #19 on issue 2109 by d...@gnu.org: do not tinker with the position
of a pitched rest
http://code.google.com/p/lilypond/issues/detail?id=2109
The ongoing discussion does not appear to jibe with the label "Fixed".
Changing to "Started".
___
Comment #18 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
ah, you compare _those_ two versions. I attached the state between
d10ec4f5 and 9f24e79a. look how the middle staff is broken; I trac
Comment #17 on issue 2109 by k-ohara5...@oco.net: do not tinker with the
position of a pitched rest
http://code.google.com/p/lilypond/issues/detail?id=2109
The regression test 'rest-on-nonstandard-staff.ly' has input indicating
half-rest half-rest | whole-rest | whole-rest |
in parallel in
Comment #16 on issue 2109 by elu...@gmail.com: do not tinker with the
position of a pitched rest
http://code.google.com/p/lilypond/issues/detail?id=2109
maybe a little note/warning/"known issue" in the docs would reduce more
confusion:
in NR after:
"1.2.2 Writing rests
Rests are entered
Comment #15 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
the regression test demonstrates that pitched rests were not always at the
prescribed vertical position and now they are; default whole
Comment #14 on issue 2109 by k-ohara5...@oco.net: do not tinker with the
position of a pitched rest
http://code.google.com/p/lilypond/issues/detail?id=2109
Assuming the input code for comment 13 was
\new Staff \with {
\override StaffSymbol #'line-count = 6 % also 5, and 7
} \relative
Comment #13 on issue 2109 by elu...@gmail.com: do not tinker with the
position of a pitched rest
http://code.google.com/p/lilypond/issues/detail?id=2109
it is too confusing with these 5, 6 or 7 lines - I simply attach 2 files
with the output of version 2.15.1 and 27:
may somebody else try
Comment #12 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
I'd say this too is "invalid" or "needs evidence" since "if I extend the
staff by a line..." (http://codereview.appspot.com/5434061/) m
Comment #11 on issue 2109 by elu...@gmail.com: do not tinker with the
position of a pitched rest
http://code.google.com/p/lilypond/issues/detail?id=2109
I'd say this too is "invalid" or "needs evidence" since "if I extend the
staff by a line..." (http://codereview.appspot.com/5434061/) move
lilypond-4 wrote:
>
>
> Comment #10 on issue 2109 by pkx1...@gmail.com: do not tinker with the
> position of a pitched rest
> http://code.google.com/p/lilypond/issues/detail?id=2109
>
> https://code.google.com/p/lilypond/issues/detail?id=2249
>
> Is now marked as invalid. So can we verify t
Comment #10 on issue 2109 by pkx1...@gmail.com: do not tinker with the
position of a pitched rest
http://code.google.com/p/lilypond/issues/detail?id=2109
https://code.google.com/p/lilypond/issues/detail?id=2249
Is now marked as invalid. So can we verify this?
__
Comment #9 on issue 2109 by elu...@gmail.com: do not tinker with the
position of a pitched rest
http://code.google.com/p/lilypond/issues/detail?id=2109
this issue cannot be verified since there are underlying problems with the
positioning of ledger lines and pitched rests - see
https://co
Updates:
Status: Fixed
Labels: -Patch-push
Comment #8 on issue 2109 by janek.li...@gmail.com: do not tinker with the
position of a pitched rest
http://code.google.com/p/lilypond/issues/detail?id=2109
pushed as 9f24e79a945ec4ab000d3e09ff2d2ac8208e2246
Sorry for the delay and ma
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-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:
Status: Started
Comment #2 on issue 2109 by pkx1...@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.)
___
bug-lilypond ma
Updates:
Labels: Patch-needs_work
Comment #1 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#c1
Patchy the autobot says: patch does not apply to current master
_
Status: Accepted
Owner:
Labels: Type-Enhancement Patch-new
New issue 2109 by gra...@percival-music.ca: do not tinker with the position
of a pitched rest
http://code.google.com/p/lilypond/issues/detail?id=2109
asdf
http://codereview.appspot.com/5434061/
22 matches
Mail list logo
