Joe Neeman schreef:
OK, I have a snapshot of 1.8.0 working, but that doesn't help. It has
something to do with the sorting of elements. As far as I can tell, this
is what's happening:
InstrumentName Piano's support contains
VerticalAxisGroup's elements contains
InstrumentName Right's supp
On Tue, 2006-06-06 at 10:17 +0200, Han-Wen Nienhuys wrote:
> Joe Neeman schreef:
> > On Tue, 2006-06-06 at 09:18 +0200, Han-Wen Nienhuys wrote:
> >> Joe Neeman schreef:
> >>> Just to make things a bit weirder, I have a working copy with
> >>> modifications that _should_ be completely irrelevant (th
Joe Neeman schreef:
On Tue, 2006-06-06 at 09:18 +0200, Han-Wen Nienhuys wrote:
Joe Neeman schreef:
Just to make things a bit weirder, I have a working copy with
modifications that _should_ be completely irrelevant (the
spacing-stick-out patch). In this working copy, I get the second png
file no
On Tue, 2006-06-06 at 09:18 +0200, Han-Wen Nienhuys wrote:
> Joe Neeman schreef:
> > Just to make things a bit weirder, I have a working copy with
> > modifications that _should_ be completely irrelevant (the
> > spacing-stick-out patch). In this working copy, I get the second png
> > file no matte
Joe Neeman schreef:
Just to make things a bit weirder, I have a working copy with
modifications that _should_ be completely irrelevant (the
spacing-stick-out patch). In this working copy, I get the second png
file no matter what.
Can anyone shed light on this?
This could be a nasty bug caused
When I "make web" a clean lilypond CVS version, instrument-name.ly
compiles to the first attached png file. If I do
$ rm input/regression/out-www/lily-409* input/regression/out-www/coll*
$ make web
I get the second attached png file. I also get the second attached png
file if I try to generate it
