droundy:
On Mon, Jun 11, 2007 at 10:32:11AM -0500, Spencer Janssen wrote:
Also nice would be the ability to catch exceptions in the X monad (as discussed before). It seems that xlib crashes when I try to find the width of a string. I'd enjoy not having to log in again when this happens.
The ability to catch exceptions would be nice, but it's hard to say how such a facility should work. Do we roll back state on an exception? We have to be careful here because there are certain state components (like mapped, waitingUnmap) that bring dire consequences when lost.
Obviously thought would need to go into it, and we'd only explicitely catch exceptions--particularly when calling user-defined code.
Furthermore, I think that catching errors in layouts is the wrong attitude: we want xmonad to crash in these early development stages to reveal bugs.
I disagree.
For xmonad hackers, I suggest using a wrapper script that restarts xmonad when it returns with a non-zero exit code.
Not a bad idea, but for the moment I suspect that all xmonad users are xmonad hackers. And since the only way to configure xmonad is to hack its
I note today I was at a workshop (yes, a programming languages one...) but there were 3 xmonad users in the room. Only one was an xmonad hacker :-) -- Don