[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Guile 2.2]
|
From: |
Thomas Morley |
|
Subject: |
Re: [Guile 2.2] |
|
Date: |
Wed, 15 Mar 2017 00:30:02 +0100 |
2017-03-15 0:17 GMT+01:00 David Kastrup <address@hidden>:
> Thomas Morley <address@hidden> writes:
>
>> 2017-03-14 23:53 GMT+01:00 Thomas Morley <address@hidden>:
>>> 2017-03-12 15:52 GMT+01:00 Thomas Morley <address@hidden>:
>>
>>
>>> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>>> scheme-engraver.ly
>>> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>>>
>>> $ lilypond-git-guile-2.2 scheme-engraver.ly
>>> GNU LilyPond 2.19.57
>>> Processing `scheme-engraver.ly'
>>> Parsing...
>>> Interpreting music...Passing a number to format as the port is deprecated.
>>> Pass (current-error-port) instead.
>>> [...]
>>> Success: compilation successfully completed
>>
>>
>> I guess this may be fixed pretty easily by replacing all instancies of
>> (format 1 ...)
>> with
>> (format #t ...)
>
> Wouldn't that be (current-output-port) rather than (current-error-port) ?
Tbh, I didn't research what (format 1 ...) was supposed to mean.
Though as a user I would want to see the output in terminal, which is
the default (current-output-port), afaik. Thus I suggest format #t.
Am I wrong?
Cheers,
Harm
Cheers,
Harm