[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 2436 in lilypond: Patch: Directs displaying-grob-ancestry.ly t
From: |
lilypond |
Subject: |
Re: Issue 2436 in lilypond: Patch: Directs displaying-grob-ancestry.ly to stderr |
Date: |
Sun, 25 Mar 2012 20:20:35 +0000 |
Comment #3 on issue 2436 by address@hidden: Patch: Directs
displaying-grob-ancestry.ly to stderr
http://code.google.com/p/lilypond/issues/detail?id=2436
As a general rule, both stdout and stderr are displayed on the terminal.
As I understand it, unix programs generally sent program output to stdout
and other "progress" or "warning" information to stderr. The image
processing programs like pngtopnm are examples of this. So - if lily
followed this paradigm, it would actually send its output (pdg, midi, etc)
to stdout, and the other informative messages to stderr. Thus, anything
not connected with the desired program output _should_ be sent to stderr.
Capturing this is no more difficult than stdout. So - for the benefit of
make doc (and following GOP9), 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 processs.
For oi polloi, both appear on the termianl anyway, so there is no change.