> Usually, this would be 'bug-lily...@gnu.org',
Typo, must be 'bug-lilyp...@gnu.org'.
Werner
> The documentation that needs to be updated is at
> https://lilypond.org/doc/v2.25/Documentation/internals/scheme-functions#index-ly_003aexpect_002dwarning
>
> I'm not familiar with the documentation modification process of
> LilyPond. Which mailing list should I send the issue to?
Usually, t
viable initial configuration found: may not find good beam slope
> >
> > I learned from other threads that this warning is generally harmless, and
> > can
> > be suppressed by something like
> >
> > #(ly:expect-warning "no viable initial configuration fo
t a warning is spat out by LilyPond (in Chinese):
>
> 没有可用的起始构型：可能找不到合适的符尾倾角
>
> Or, in English:
>
> no viable initial configuration found: may not find good beam slope
>
> I learned from other threads that this warning is generally harmless, and
> can
> be suppressed
find good beam slope
I learned from other threads that this warning is generally harmless, and can
be suppressed by something like
#(ly:expect-warning "no viable initial configuration found")
However, this only works when the language environment variable is set to
English (`LANGU
On Sat, Sep 28, 2019 at 4:42 PM Aaron Hill wrote:
> On 2019-09-28 4:09 pm, Knute Snortum wrote:
> > I haven't been able to get the ly:expect-warning function working
> > properly. Here is a MWE:
> >
> > %%% Start
> > \version "2.19.83"
>
On 2019-09-28 4:09 pm, Knute Snortum wrote:
I haven't been able to get the ly:expect-warning function working
properly. Here is a MWE:
%%% Start
\version "2.19.83"
\include "english.ly"
#(ly:expect-warning "omitting tuplet bracket")
{
\clef bass
\tupl
I haven't been able to get the ly:expect-warning function working
properly. Here is a MWE:
%%% Start
\version "2.19.83"
\include "english.ly"
#(ly:expect-warning "omitting tuplet bracket")
{
\clef bass
\tuplet 3/2 4 {
<<
{ g4 s8 gf4 s8 f4
"Trevor Daniels" writes:
> David, you wrote Monday, June 05, 2017 5:34 PM
>
>
>> Richard Shann writes:
>>
>>> I found by trial-and-error that if I remove any of the three occurrences
>>> of the ly:expect-warning the warning returns.
>>&
David, you wrote Monday, June 05, 2017 5:34 PM
> Richard Shann writes:
>
>> I found by trial-and-error that if I remove any of the three occurrences
>> of the ly:expect-warning the warning returns.
>>
>> Where should it be called?
>
> At the top, once for
> >>
> >> Sometimes one has to accept warnings, so in future situations
> >> ly:expect-warning might be your friend (unless it is banned from
> >> Mutopia? I’d be surprised). It only needs the beginning of the warning
> >> string, like
> >> #(l
Richard Shann writes:
> On Sun, 2017-06-04 at 17:48 +0200, Simon Albrecht wrote:
>> On 04.06.2017 15:50, Knute Snortum wrote:
>> > I post to Mutopia so I can't have warnings. Any thoughts?
>>
>> Sometimes one has to accept warnings, so in future situations
On Sun, 2017-06-04 at 17:48 +0200, Simon Albrecht wrote:
> On 04.06.2017 15:50, Knute Snortum wrote:
> > I post to Mutopia so I can't have warnings. Any thoughts?
>
> Sometimes one has to accept warnings, so in future situations
> ly:expect-warning might be your friend (u
(if (> c 0)
(begin
(ly:expect-warning message)
(loop (1- c))
#(suppress "MIDI channel wrapped around" 5)
#(suppress "remapping modulo 16" 5)
Note there's also a warning for expected error NOT encountere
instance, so you need to repeat it for each
warning. I don't know the rationale for this. In any case, you could put
something like this at the head of your file. I guess copy-and-paste would
be equally effective :)
#(define (suppress message x)
(let loop ((c x))
(if (> c 0)
Hello,
I just tried to suppress a series of expected warnings, but the scheme
function seems to suppress only the first of a kind. See attached file.
Why is this?
Best regards,
Simon
\version "2.19.3"
#(ly:expect-warning "MIDI channel wrapped around")
#(ly:expect-warni
16 matches
Mail list logo
