<lilypond <at> googlecode.com> writes: > Comment #3 on issue 2436 by [email protected]: Patch: Directs > > I'm trying to ensure that all progress messages go to stderr, > not stdout. A by-product of this is that they are captured in > logfiles during make test and can also be checked as part of > the regression testing process. >
It is arguable whether the ancestry listings are progress messages or program output. The hoi polloi won't use that snippet at all, but those they do use it probably do something like C:> lilypond displaying-grob-ancestry.ly >out.txt 2>err.txt and will be mildly inconvenienced when the ancestry listings have other progress messages interspersed. I think it's fine to inconvenience them in this case. The similar but more widely useful function \displayLilyMusic that is included in LilyPond has your optional output-port argument, which is great for making everybody happy. _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
