Comment #41 on issue 1110 by d...@gnu.org: Wrong octave of repetition chord
with \relative and #{ #} syntax
http://code.google.com/p/lilypond/issues/detail?id=1110#c41
Remove basically all configurability. Reduce parser and lexer support
to hardwired minimum. Don't track the last chord in t
Comment #40 on issue 1110 by d...@gnu.org: Wrong octave of repetition chord
with \relative and #{ #} syntax
http://code.google.com/p/lilypond/issues/detail?id=1110#c40
Fix compatibility function.
http://codereview.appspot.com/5595043
___
bug-lily
Comment #39 on issue 1110 by d...@gnu.org: Wrong octave of repetition chord
with \relative and #{ #} syntax
http://code.google.com/p/lilypond/issues/detail?id=1110
First: I have no idea why git-cl chose to create a new codereview issue for
this one-line change.
Second: if you ran patchy f
Updates:
Labels: Patch-new
Comment #38 on issue 1110 by d...@gnu.org: Wrong octave of repetition chord
with \relative and #{ #} syntax
http://code.google.com/p/lilypond/issues/detail?id=1110#c38
Fix compatibility function.
http://codereview.appspot.com/5595043
_
Updates:
Status: Fixed
Labels: fixed_2_15_27
Comment #3 on issue 1352 by k-ohara5...@oco.net: Polyphonic dots placement
is inconsistent, confusing and prone to collisions
http://code.google.com/p/lilypond/issues/detail?id=1352
I propose that the Consistency and Collision aspec
-Eluze gmail.com> writes:
> to me the dots seem to far away from noteheads and the regular distance of
> equivalent durations is broken without a need (2nd measure)
Yes, the dots are too far from the note heads. The code uses rectangular
boxes in place of the real shapes of the flags to decide
Updates:
Labels: Patch-needs_work
Comment #37 on issue 1110 by lilypond...@gmail.com: Wrong octave of
repetition chord with \relative and #{ #} syntax
http://code.google.com/p/lilypond/issues/detail?id=1110#c37
Patchy the autobot says: patch does not apply to current master, yes I ran
>> \header { texidoc = "
>> A broken ottava spanner must not interfere with @code{\\tempo} and
>> @code{\\time}.
>
> Well, the ottava does not interfere with the tempo or the time.
> In fact, it seems to try to hard to avoid them.
Yes, this is sloppy wording. It should be rather `the horizont
googlecode.com> writes:
> \header { texidoc = "
> A broken ottava spanner must not interfere with @code{\\tempo} and
> @code{\\time}.
Well, the ottava does not interfere with the tempo or the time.
In fact, it seems to try to hard to avoid them.
I assume the desired behavior is to put the 8v
Updates:
Summary: line-broken spanners start too far to the right, with \tempo and
\time
Comment #5 on issue 2260 by k-ohara5...@oco.net: line-broken spanners start
too far to the right, with \tempo and \time
http://code.google.com/p/lilypond/issues/detail?id=2260
Most spanners try to sta
Phil Holmes philholmes.net> writes:
> Think this is previously unreported.
I agree.
It is related to http://code.google.com/p/lilypond/issues/detail?id=727
We might fix both by treating the old-style pedal marks as a text-spanner.
Then the Ped and * are always horizontally aligned (issue 727
Status: Accepted
Owner:
Labels: Type-Ugly
New issue 2261 by pkx1...@gmail.com: Sustain off placement bug
http://code.google.com/p/lilypond/issues/detail?id=2261
{
<<
\new Staff
<<
\new Voice{
s2 \sustainOn s4 s4 \sustainOff s1 s2 \sustainOn s4 s8
\sustainOff s8 s1
Hello,
On 28 January 2012 18:48, Phil Holmes wrote:
> Think this is previously unreported. It came from a real score I've been
> working on, which has all manner of other stuff like change staff in it -
> took ages to prune it back to this:
>
> {
> <<
> \new Staff
> <<
> \new Voice{
>
Updates:
Labels: Patch-review
Comment #13 on issue 2259 by lilypond...@gmail.com: Hairpin still hits
barline at line break
http://code.google.com/p/lilypond/issues/detail?id=2259#c13
Patchy the autobot says: LGTM.
___
bug-lilypond mailing
Updates:
Labels: Patch-new
Comment #36 on issue 1110 by d...@gnu.org: Wrong octave of repetition chord
with \relative and #{ #} syntax
http://code.google.com/p/lilypond/issues/detail?id=1110#c36
Reimplement ChordRepetition facility.
Remove basically all configurability. Reduce parse
Think this is previously unreported. It came from a real score I've been
working on, which has all manner of other stuff like change staff in it -
took ages to prune it back to this:
{
<<
\new Staff
<<
\new Voice{
s2 \sustainOn s4 s4 \sustainOff s1 s2 \sustainOn s4 s8
\
Updates:
Labels: -Type-Ugly Type-Critical Regression
Comment #4 on issue 2260 by philehol...@gmail.com: broken ottava spanner
interferes with \tempo and \time
http://code.google.com/p/lilypond/issues/detail?id=2260
Broken between 2.13.31 and 2.13.34.
Updates:
Status: New
Owner: ---
Cc: -al...@alfarrabio.di.uminho.pt
Labels: -Patch-needs_work
Comment #6 on issue 2134 by pkx1...@gmail.com: Redirect old website /
download to new location
http://code.google.com/p/lilypond/issues/detail?id=2134
(No comment was e
Comment #3 on issue 2260 by lemzw...@gmail.com: broken ottava spanner
interferes with \tempo and \time
http://code.google.com/p/lilypond/issues/detail?id=2260
OK. Can someone test this, please? BTW, here an even simpler input file.
{
\ottava #-1 e'1 \time 4/4 \break |
\tempo 4 = 90 e'1
Updates:
Labels: -Type-Critical Type-Ugly
Comment #2 on issue 2260 by gra...@percival-music.ca: broken ottava spanner
interferes with \tempo and \time
http://code.google.com/p/lilypond/issues/detail?id=2260
Unless this was displayed correctly in 2.12.3, it is not a Critical
regressi
Comment #1 on issue 2260 by lemzw...@gmail.com: broken ottava spanner
interferes with \tempo and \time
http://code.google.com/p/lilypond/issues/detail?id=2260
(No comment was entered for this change.)
Attachments:
ottava-tempo-time.png 16.7 KB
_
Status: Accepted
Owner:
CC: ste...@lemberg.at
Labels: Type-Critical
New issue 2260 by lemzw...@gmail.com: broken ottava spanner interferes with
\tempo and \time
http://code.google.com/p/lilypond/issues/detail?id=2260
version "2.15.25"
\header { texidoc = "
A broken ottava spanner must n
Comment #19 on issue 1964 by gra...@percival-music.ca: lilydev 2.0
http://code.google.com/p/lilypond/issues/detail?id=1964
there's an improved git-cl on my github account now:
https://github.com/gperciva/git-cl
Thanks to Lukasz Czerwinski, it tracks all lilypond patches with the same
base url
lilypond-4 wrote:
>
> Updates:
> Status: Fixed
> Labels: fixed_2_15_27
>
> Comment #2 on issue 1230 by k-ohara5...@oco.net: Dot may collide with flag
> with some stem's 'length values
> http://code.google.com/p/lilypond/issues/detail?id=1230
>
>
to me the dots seem to far away f
24 matches
Mail list logo
