Reviewers: dak, Graham Percival,
Message:
Please review minor change.
Description:
The regtest option-help.ly prints out the help string for ly:set-option,
with the intention of making this testable via logfile comparison.
However, it sends the output to stdout, so it appears on the terminal
On 2012/02/04 12:45:23, PhilEHolmes wrote:
Please review minor change.
If we have a Scheme function for printing, the output should not be
hardwired to a non-Scheme port, whether that be stderr or stdout. I
think I mentioned as much.
I'll push a reimplementation to staging in the next half
On 2012/02/04 15:08:33, dak wrote:
On 2012/02/04 12:45:23, PhilEHolmes wrote:
Please review minor change.
If we have a Scheme function for printing, the output should not be
hardwired to
a non-Scheme port, whether that be stderr or stdout. I think I
mentioned as
much.
I'll push a
See new description. Please review.
http://codereview.appspot.com/5625052/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 2012/02/04 17:34:09, PhilEHolmes wrote:
See new description. Please review.
Well, obviously correct, but it will still require one pass of the
staging patchy before the testing patchy will be happy with it. So
depending on who runs which Patchy when, this might take some time to
get the
- Original Message -
From: d...@gnu.org
To: philehol...@googlemail.com; gra...@percival-music.ca
Cc: re...@codereview-hr.appspotmail.com; lilypond-devel@gnu.org
Sent: Saturday, February 04, 2012 5:40 PM
Subject: Re: Directs lilypond option help to stderr (issue 5625052)
On 2012/02/04
