Re: Debug output etc, cluttering the terminal
Hello,
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> On Sun, Aug 15, 2010 at 12:09:42AM +0100, Neil Williams 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.
>
> The Unix tradition is for programs to run silently unless there's a
> problem. Taking 64ms to complete some operation is not, in general, a
> problem.
Yepp, citing the rule of silence from TAOUP: '...when a program has
nothing interesting or surprising to say, it should shut up.'
Regards
hmw
--
biff4emacsen - A biff-like tool for (X)Emacs
http://www.c0t0d0s0.de/biff4emacsen/biff4emacsen.html
Flood - Your friendly network packet generator
http://www.c0t0d0s0.de/flood/flood.html
Reply to: