[xmonad] Avoiding multiple status bar processes after XMonad restart

Brandon Allbery allbery.b at gmail.com
Sat Jan 14 23:23:45 CET 2012

On Sat, Jan 14, 2012 at 16:23, Jacek Generowicz <jacek.generowicz at cern.ch>wrote:

> Would you have any advice on avoiding multiple xmobar or dzen
> processes running as a consequence of XMonad restarts?

You should only be starting them from xmonad as part of DynamicLog, in
which case they go away when the xmonad that started them does.

If you must start things not over a pipe from the startup hook (this is
strongly disrecommended; this is what ~/.xsession is for), you can check
for command line arguments.

    , startupHook = do args <- getArgs
                      guard (null args) $ spawn "xmobar"

brandon s allbery                                      allbery.b at gmail.com
wandering unix systems administrator (available)     (412) 475-9364 vm/sms
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/xmonad/attachments/20120114/005e13dc/attachment.htm>

More information about the xmonad mailing list