On Mon, 2009-01-12 at 03:37 +0100, Valentin Villenave wrote:
> 2009/1/12 Joe Neeman :
>
> > BTW Valentin, I think the appropriate response here would be to remove
> > the "Fixed" label. "Fixed," to me, means "I think I've fixed it, can
> > someone please check." If the status is left as Fixed, I p
2009/1/12 Joe Neeman :
> BTW Valentin, I think the appropriate response here would be to remove
> the "Fixed" label. "Fixed," to me, means "I think I've fixed it, can
> someone please check." If the status is left as Fixed, I probably won't
> look at the bug when I'm next browsing the bug list.
Y
On Sun, 2009-01-11 at 17:04 -0800, Mark Polesky wrote:
> Valentin Villenave wrote:
>
> > 2009/1/12 Mark Polesky :
> >
> > > I don't consider this issue "fixed".
> >
> > Mark, I've added your comment and your example. However, do keep in
> > mind that the status for closed issues is "verified", n
Valentin Villenave wrote:
> 2009/1/12 Mark Polesky :
>
> > I don't consider this issue "fixed".
>
> Mark, I've added your comment and your example. However, do keep in
> mind that the status for closed issues is "verified", not "fixed", and
> this is not "verified" yet.
>
> Another comment: ple
2009/1/12 Mark Polesky :
> I don't consider this issue "fixed".
Mark, I've added your comment and your example. However, do keep in
mind that the status for closed issues is "verified", not "fixed", and
this is not "verified" yet.
Another comment: please use extra diplomacy (and patience) whenev
Comment #3 on issue 726 by v.villenave: Wrong accidentals alignment when a
second occurs simultaneously
http://code.google.com/p/lilypond/issues/detail?id=726
Hmm. Looks a bit funny though; are we sure we want to keep this rule?
New comment from Mark:
Ted Ross (pp.130-135) demonstrates that
> Comment #2 on issue 726 by joeneeman: Wrong accidentals alignment when a
> second occurs simultaneously
> http://code.google.com/p/lilypond/issues/detail?id=726
>
> The behaviour for the first example is explained by the fact that we align
> accidentals belonging to the same octave.
But that
Updates:
Status: Fixed
Labels: fixed_2_12_2
Comment #2 on issue 726 by joeneeman: Wrong accidentals alignment when a
second occurs simultaneously
http://code.google.com/p/lilypond/issues/detail?id=726
The behaviour for the first example is explained by the fact that we align
a
Updates:
Summary: Wrong accidentals alignment when a second occurs simultaneously
Cc: joeneeman
Comment #1 on issue 726 by v.villenave: Wrong accidentals alignment when a
second occurs simultaneously
http://code.google.com/p/lilypond/issues/detail?id=726
A related example from
