lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Output from woodwind-diagrams-key-lists.ly


From: David Kastrup
Subject: Re: Output from woodwind-diagrams-key-lists.ly
Date: Sun, 18 Dec 2011 13:19:10 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.92 (gnu/linux)

David Kastrup <address@hidden> writes:

> "Phil Holmes" <address@hidden> writes:
>
>> ----- Original Message ----- 
>> From: "Keith OHara" <address@hidden>
>> To: <address@hidden>
>> Sent: Saturday, December 17, 2011 7:04 PM
>> Subject: Re: Output from woodwind-diagrams-key-lists.ly
>>
>>
>>> mike <at> apollinemike.com <mike <at> apollinemike.com> writes:
>>>
>>>> This regtest makes sure that the key-name function works for all
>>>> instruments - I'd be open to other options
>>>
>>> Just to be clear, Phil strongly suspects that the output is not checked,
>>> so if I accidentally broke the key-name function to print something wrong,
>>> nobody would notice (until somebody sees the mistake in the docs, and that
>>> path doesn't even use the regtest).
>>>
>>> I like David's redirection idea, sending to dev/null if the purpose is to
>>> exercise the key-name function, or to stderr if the purpose is to flag
>>> changed output.
>>
>> Seconding this, it seems to me the best option is todo a small rewrite
>> of display-woodwind-diagrams.scm so that either it defaults to sending
>> output to stderr, or that there's an option to direct output to
>> stdout, stderr, dev/null or whatever.  Unfortunately I've looked at
>> the file and don't have a clue as to how to do this.  Can anyone else
>> offer help?
>
> Ok, I'll do that.  It is not all that much work.

There you are.  It sounds like you might want to use
(current-error-port) for the optional port argument in the regtest.

-- 
David Kastrup




reply via email to

[Prev in Thread] Current Thread [Next in Thread]