Bug#576188: [pkg-cli-apps-team] Bug#576188: Bug#576188: banshee: Outputs loads of junk to STDOUT

[Antony Gelberg]

Chow Loong Jin wrote:
> 
> Then tell me, exactly what do you hope to achieve by opening Banshee in a
> terminal instead of using a graphical approach, e.g. the menu?
> 

Is this a serious question?  I will assume it is and give a straight answer.

The answer is: I am hoping to run the application.

> FYI, all Glib applications spit information -- warnings, errors, other
> information out into the terminal regardless of any debug flag. I do not see
> this as a problem.
> 

If you don't see it as a problem, it's probably because you are only
ever clicking on icons to open applications, STDOUT is redirected to
.xsession-errors or a bitbucket or $somewhere_else, and you assume that
everybody does that.  However for some users it clearly is a problem.

If it wants to write to STDERR to report something exceptional then
that's different, but as I said originally, routinely clobbering STDOUT
with junk is unacceptable.

> Banshee does the same, just on a slightly larger scale.  And the --debug flag
> exists to spit out even more information than is already spat out to the 
> terminal.
> 

Great.  But I'm looking for less, not more.

Antony



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#576188: [pkg-cli-apps-team] Bug#576188: Bug#576188: banshee: Outputs loads of junk to STDOUT

[Chow Loong Jin]

On Friday 23,April,2010 05:31 PM, Antony Gelberg wrote:
> Chow Loong Jin wrote:
>> On Thursday 01,April,2010 06:59 PM, Antony Gelberg wrote:
>>> Package: banshee
>>> Version: 1.0.0-1
>>> Severity: normal
>>>
>>> As per subject really, banshee fills my console with a load of messages that
>>> are at best useful for debug.  Clobbering STDOUT is really not cricket.
>>
>> I don't see what the problem is. A graphical application is usually not 
>> started
>> from the terminal, unless you are looking for debugging information. Are you
>> really hoping to interact with Banshee from the console? If you are, then 
>> sorry,
>> but I don't believe it is planned to give Banshee a command line interface 
>> any
>> time soon.
>>
> 
> I think your assumption that "A graphical application is usually not
> started from the terminal, unless you are looking for debugging
> information." is utterly flawed.  These messages should be printed only
> when some debug flag is switched on.
> 
> I am not hoping to "interact" with Banshee from the command line, and I
> never said I was.

Then tell me, exactly what do you hope to achieve by opening Banshee in a
terminal instead of using a graphical approach, e.g. the menu?

FYI, all Glib applications spit information -- warnings, errors, other
information out into the terminal regardless of any debug flag. I do not see
this as a problem.

Banshee does the same, just on a slightly larger scale. And the --debug flag
exists to spit out even more information than is already spat out to the 
terminal.

-- 
Kind regards,
Chow Loong Jin (GPG: 0x8F02A411)
Ubuntu Developer



signature.asc
Description: OpenPGP digital signature