2009/7/30 Reinhold Kainhofer :
> How would you fix this? By default, the TimeSignature Grob does not have the
> text-interface, however, if you use the #ly:text-interface::print function as
> stencil, you need to set the text...
grob-interpret-markup
>> MusicXML programming errors:
>>
>> 42a-Mul
On Wed, Jul 29, 2009 at 11:47:07PM +0100, Neil Puttock wrote:
> 2009/7/29 Patrick McCarty :
>
> > Some of the programming errors from the regression tests are pretty
> > bizarre, but I'll try taking a look at some of them eventually. :-)
>
> To help you get started, here's a text file I've compi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Donnerstag, 30. Juli 2009 00:47:07 schrieb Neil Puttock:
> 2009/7/29 Patrick McCarty :
> > Some of the programming errors from the regression tests are pretty
> > bizarre, but I'll try taking a look at some of them eventually. :-)
>
> To help you g
2009/7/29 Neil Puttock :
> regtests which should produce errors? We can't set warning-as-error
> for these
Oops, I mean unset warning-as-error. :)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
2009/7/29 Patrick McCarty :
> Some of the programming errors from the regression tests are pretty
> bizarre, but I'll try taking a look at some of them eventually. :-)
To help you get started, here's a text file I've compiled with my
thoughts on the remaining issues; some of them are easily fixe
On Fri, Jul 17, 2009 at 12:33:11AM +0100, Neil Puttock wrote:
> 2009/7/16 Patrick McCarty :
>
> > 2.) Fix the regression tests that are supposed to compile without any
> > warnings or programming errors. (This is the long-term project)
>
> There shouldn't be too many of these, since I cleared up
2009/7/16 Patrick McCarty :
> Step 3.) might be a few years away, but IMO, this should be on the
> tracker so it is not lost.
I hear you.
http://code.google.com/p/lilypond/issues/detail?id=814
Regards,
Valentin
___
bug-lilypond mailing list
bug-lilyp
2009/7/16 Patrick McCarty :
> 2.) Fix the regression tests that are supposed to compile without any
> warnings or programming errors. (This is the long-term project)
There shouldn't be too many of these, since I cleared up a load last
year; what remains is most likely to be programming errors, w
. This will be a "stress
test" for the regression tests, since we don't want our regression
tests emitting warnings or programming errors unintentionally.
***
The following steps need to be taken for this to happen:
1.) Disable the option for every regression test that *intent
