[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-bug
Subject:    Re: lilypond-book
From:       David Kastrup <dak () gnu ! org>
Date:       2014-03-17 6:32:32
Message-ID: 87y5099vy7.fsf () fencepost ! gnu ! org
[Download RAW message or body]

Julien Rioux <jrioux@lyx.org> writes:

> On 16/03/2014 5:08 PM, David Kastrup wrote:
>> <URL:http://code.google.com/p/lilypond/issues/detail?id=3874>
>>
>> Marked as backport, tested satisfactorily, forgot to cherry-pick into
>> stable/2.18.
>>
>> Phil, hold the horses until I got that one in.
>>
>> Thanks for noticing.
>
> OK thanks, so there were multiple reports of the same problem. Good to
> know that it's been taken care of.

Half and half.  On Windows, the exit function does not seem to work, and
in spite of numerous requests from me, nobody bothered checking variants
and see what might and might not work for whatever reason.

While it "only" results in misleading and useless backtraces when Python
was supposed to exit anyway, it would be definitely reasonable to get
rid of that.

-- 
David Kastrup


_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
[prev in list] [next in list] [prev in thread] [next in thread]