Re: [Xmonad] darcs patch: make spawn redirect std* to /dev/null

Bruce Stephens writes:

Bruce Stephens writes:

[...]

...

That would do. Would be cleaner, IMHO, for the logHook output to go somewhere else. Then in a normal setup you'd get the logging from clients in .xsession-errors, whether those started before xmonad or by xmonad.

I guess the simplest way would be to use the more conventional arrangement of xmonad starting the program (whether dzen2 or something else) that displays the information?

Most of the programs by convention expect output from a sub-shell to also contain the output from the sub-shells within that sub-shell. Usually xdm or alike redirect those outputs from programs started by it and ~/.xsession and subsequent calls to ~/.xsession-errors. Normally, it's useless, but when something goes wrong, that is the first place to seek for insights. So I would think that redirecting the std{out,err} to /dev/null is bad. Since we can not force all other programs to make their own log files, the best way I believe is that to redirect the output of logHook. And I would suggest using FIFOs (named pipes) as a good solution for logHook to give its information to various displaying programs like dzen, xmobar or something similar. -- c/* __o/* <\ * (__ */\ <