Issue 427 in xmonad: xmonad should recompile configuration on SIGHUP
Status: New Owner: ---- New issue 427 by moreil...@gmail.com: xmonad should recompile configuration on SIGHUP http://code.google.com/p/xmonad/issues/detail?id=427 in unix it's common convention for long-lived processes to re-read configuration and restart on receiving a HUP signal. to my surprise xmonad does not follows this.
Comment #1 on issue 427 by gwe...@gmail.com: xmonad should recompile configuration on SIGHUP http://code.google.com/p/xmonad/issues/detail?id=427 I haven't tested this, but I think this ought to be quite easy to support - perhaps as simple as hunk ./XMonad/Core.hs 508 + installHandler sigHUP (CatchOnce (recompile True >> return ())) Nothing
Comment #2 on issue 427 by allber...@gmail.com: xmonad should recompile configuration on SIGHUP http://code.google.com/p/xmonad/issues/detail?id=427 That's actually a convention for servers, which usually have no other way to get notified of need to reload. Since I can think of at least two ways to ask xmonad to reload its configuration, it isn't really needed here.
Comment #3 on issue 427 by moreil...@gmail.com: xmonad should recompile configuration on SIGHUP http://code.google.com/p/xmonad/issues/detail?id=427 such feature may come in handy in case of xmonad lockup caused by some misbehaving extension, x.prompt for example. under such circumstances xmonad --restart usually does not makes any effect (regular input locked up too).
participants (1)
-
codesite-noreply＠google.com