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

Reply via email to