Re: Debug output etc, cluttering the terminal
On Sun, Aug 15, 2010 at 7:09 AM, Neil Williams <email@example.com> wrote:
> It's debug output, it is useful when debugging and you need the output,
> e.g. when fixing bugs and the user can just be asked to run the command
> from the terminal and post the output to help in debugging the bug
> report. Generally, the debug output for a particular release tends to
> reflect the issues which upstream were working on most intensively
> before that release and therefore can have a direct impact on the
> likelihood of new bugs or regressions in old bugs.
> It's not clutter. If you don't want to see it, run the command and
> redirect stderr.
debug output should certainly not be output by default in released
versions without a command-line or configuration option turning it on.
l for one don't want ls doing something like this:
ls: starting up
ls: checking for bad filesystems
ls: searching for files in /home/foo/some/path
foo bar/ baz/
ls: 1 file found
ls: 2 directories found