On Sun, Jan 16, 2011 at 10:55:55AM +0100, David Kastrup wrote:
> I'd rather we just use
> #(regtest:expext_warning (_ "Some particular warning"))
>
> before the line being the eventual cause of some expected warning, and
> ly:warning get hijacked, matching the expected warnings to the given
> warn
>> I personally would like some functions to print output at the
>> relevant stage:
>> #(ly:warning_parser (_ "blah"))
>> #(ly:warning_translator (_ "blah"))
>> #(ly:warning_event_class (_ "blah"))
>> #(ly:warning_engraver (_ "blah"))
>> #(ly:warning_performer (_ "blah"))
>> #(ly:warnin
Graham Percival writes:
> On Sun, Jan 16, 2011 at 07:04:02AM +0100, Werner LEMBERG wrote:
>>
>> while walking through the log file I see many warnings for lilypond
>> input files. Some of them are part of the regression test,
>
> IMO those should be moved into a separate directory, intended for
On Sun, Jan 16, 2011 at 07:04:02AM +0100, Werner LEMBERG wrote:
>
> while walking through the log file I see many warnings for lilypond
> input files. Some of them are part of the regression test,
IMO those should be moved into a separate directory, intended for
such warnings.
> What about addi
Folks,
while walking through the log file I see many warnings for lilypond
input files. Some of them are part of the regression test, but some
not. An example for the former is, I think
In repeat-unfold.ly:
warning: More alternatives than repeats. Junking excess alternatives
and her a
