[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: strange replacement 100 → hundred in NR
|
From: |
Michael Käppler |
|
Subject: |
Re: strange replacement 100 → hundred in NR |
|
Date: |
Thu, 1 Oct 2020 16:03:11 +0200 |
|
User-agent: |
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 |
Am 01.10.2020 um 12:24 schrieb Jonas Hahnfeld via Discussions on
LilyPond development:
So I think it's more likely that the issue got exposed by
commit 5a957021a3 which runs lilypond once per document passed to
lilypond-book instead of per included file. This increases the chance
of being unlucky...
Another topic, but possibly related:
Could this potentially affect regtests, that
use (ly:set-option 'warning-as-error) or similar?
In the sense, that the state change triggered by ly:set-option leaks
through to other
snippets?
Btw., is it still good practise to use
the
(ly:set-option 'warning-as-error)
(ly:expect-warning ...)
construct in regtests? I vaguely remember a discussion about that some
time ago on -devel...)
Cheers,
Michael