Issue 478 in xmonad: Restart could be made more robust

Status: Accepted Owner: nicolas....@gmail.com Labels: Type-Defect Priority-Medium Usability Component-Core New issue 478 by nicolas....@gmail.com: Restart could be made more robust http://code.google.com/p/xmonad/issues/detail?id=478 Currently xmonad uses a combination of argument passing and environment variable passing in order to give the current state to the new instance of xmonad. These two channels are limited in size (and this is a practical concerned for me). Moreover using arguments pollutes the process listing and also leak some information. I would suggest reading both pieces of state from a file descriptor instead.

Comment #1 on issue 478 by allber...@gmail.com: Restart could be made more robust http://code.google.com/p/xmonad/issues/detail?id=478 I'm not sure what you're concerned about leaking, as most of the information passed on other than the layout detail is available via properties in the X server. Which is where this should be passed anyway; I'd probably attach an XMONAD_LAYOUT property to each window with its state information. This also avoids the potential for race conditions when the window state changes during the restart sequence.
participants (1)
-
codesite-noreply@google.com