[Xmonad] Issue 46 in xmonad: xmonad's output (logHook) needs to be separated from output from client programs

[codesite-noreply at google.com]

Issue 46: xmonad's output (logHook) needs to be separated from output from client programs
http://code.google.com/p/xmonad/issues/detail?id=46

New issue report by br... at cenderis.demon.co.uk:
What steps will reproduce the problem?
1. start xmonad with a logHook
2. use dmenu (or something else) to start a noisy application (firefox with
the realplayer plugin playing, say)

What is the expected output? What do you see instead?

I'd hope that the status output of logHook would still usefully show focus,
workspace state, etc.  In fact it shows "playeripc: "Got command
GetPlayerUINT32Prop 0 playstate" or similar useless rubbish.

What version of the product are you using? On what operating system?

darcs xmonad on GNU/Linux.

Please provide any additional information below.

This is at least arguably a bug in almost all X applications.  They're
printing debugging information that's almost surely useless for almost all
purposes.

However, I fear such applications aren't likely to be fixed any time soon
(it seems normal for KDE and GNOME applications to produce stupid logging
when things start up), so in the mean time it would probably be useful for
window managers to have some kind of workaround.  Perhaps have logHook to a
named pipe rather than stdout?  Or just redirect output (to /dev/null would
be fine, IMHO) from clients started using dmenu (or the XMonadContrib
alternatives)?

If this error is due to a module from XMonadContrib, please tag this issue
with 'Component-Contrib' below.

It's not, though there are modules in XMonadContrib which are also affected.


Issue attributes:
	Status: New
	Owner: ----
	Labels: Type-Defect Priority-Medium

-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings