[xmonad] Issue 588 in xmonad: xmonad --restart doesn't seem to work

[codesite-noreply at google.com]

Comment #8 on issue 588 by daniel.w... at gmail.com: xmonad --restart doesn't  
seem to work
https://code.google.com/p/xmonad/issues/detail?id=588

I don't really know what other pieces you're looking for, to be honest.  
Let's be clear about what's happening and see if you still think there's  
something missing.

Let's start the story when you log in. Your login manager starts up a  
process named xmonad, which notices that there's a configuration file named  
~/.xmonad/xmonad.hs. It builds ~/.xmonad/xmonad-arch-os, and straight away  
hands over all control to xmonad-arch-os, disappearing at the same time.

Now you come along and change xmonad.hs, then run (from your command line,  
say) xmonad --restart. So there are now two processes running:  
xmonad-arch-os, and xmonad --restart. The --restart process sets the  
XMONAD_RESTART atom and dies, leaving just one process. Then X tells  
xmonad-arch-os that the XMONAD_RESTART atom has been set; so the  
xmonad-arch-os process builds a fresh copy of the ~/.xmonad/xmonad-arch-os  
file, then hands all control over to the *new* xmonad-arch-os, disappearing  
at the same time.

Does this architecture make sense? Do you now understand how the --restart  
argument is handled, and how the code reflects that handling? If so, where  
does that leave you in terms of understanding the behavior you see  
happening?

-- 
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings