- xmonad - Haskell.org

darcs patch: use the right catch in catchX.
by David Roundy 12 Oct '07

12 Oct '07

This fixes catchX to now catch all exceptions, rather than only those which arise from a certain class of IO errors. This should be applied along with the two patches I sent previously, and together they ought to handle issue 55. David (who is thankful that is current setup just lets him run without a window manager when xmonad dies, which allows him to fix the code and compile a new one) Thu Oct 11 21:14:50 EDT 2007 David Roundy <droundy(a)darcs.net> * use the right catch in catchX. Don't ask *me* why the prelude includes a version of catch that is worse than useless (because it lulls you into a feeling of safety).

2 1

darcs patch: fix one last bug w.r.t. issue 55.
by David Roundy 12 Oct '07

12 Oct '07

Ooops. I killed my xmonad... David Thu Oct 11 21:05:09 EDT 2007 David Roundy <droundy(a)darcs.net> * fix one last bug w.r.t. issue 55.

2 1

darcs patch: catch exceptions when calling user-written code.
by David Roundy 12 Oct '07

12 Oct '07

Thu Oct 11 21:31:13 EDT 2007 David Roundy <droundy(a)darcs.net> * catch exceptions when calling user-written code. Note: this is a less-than-minimal approach, since it seemed better to put the catchX in whenJust, rather than in both times whenJust is used in Main. As a result, it does a few potentially less efficient checks, but we're also slightly more robust with regard to bugs introduced in the future.

1 0

Issue 55 in xmonad: Non-core code should be sandboxed
by codesite-noreply＠google.com 12 Oct '07

12 Oct '07

Issue 55: Non-core code should be sandboxed http://code.google.com/p/xmonad/issues/detail?id=55 Comment #5 by daveroundy: Actually, I sent in three patches, and now it's really fixed. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 55 in xmonad: Non-core code should be sandboxed
by codesite-noreply＠google.com 12 Oct '07

12 Oct '07

Issue 55: Non-core code should be sandboxed http://code.google.com/p/xmonad/issues/detail?id=55 Comment #4 by daveroundy: I've just sent in a patch to fix this. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

darcs patch: catch exceptions when calling user-written code.
by David Roundy 12 Oct '07

12 Oct '07

Note: this fixes issue 55. David Thu Oct 11 20:56:55 EDT 2007 David Roundy <droundy(a)darcs.net> * catch exceptions when calling user-written code. Note: this is a less-than-minimal approach, since it seemed better to put the catchX in whenJust, rather than in both times whenJust is used in Main. As a result, it does a few potentially less efficient checks, but we're also slightly more robust with regard to bugs introduced in the future.

1 0

Issue 54 in xmonad: Composable manageHooks interface
by codesite-noreply＠google.com 12 Oct '07

12 Oct '07

Issue 54: Composable manageHooks interface http://code.google.com/p/xmonad/issues/detail?id=54 Comment #3 by daveroundy: Note that the disadvantages mentioned in the original post are all false. Hooks that need IO to see if they need to be run *can* be written (it's just a bit more code), and it's possible to run multiple hooks per window (it's just a bit more code). I have yet to see a reason for this change. Since this feature can be added without touching core, I see no reason to add it to core before it's been tested out in contrib. David -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Possible borkage in patch for EwmhDesktops, ManageDocks and SetWMName
by Alex Tarkovsky 12 Oct '07

12 Oct '07

The patch I posted yesterday to fix building of EwmhDesktops, ManageDocks and SetWMName for amd64 may have introduced regressions. I suspect this because EwmhDesktops or SetWMName has been causing my gnome-panel to crash fairly frequently, including every time I exit Gimp. Joachim, can you please review the whole patch? (You can safely ignore the whitespace fixes. ;) ) -- Alex Tarkovsky

4 3

darcs patch: Fix EwmhDesktops, ManageDocks, and SetWMName compilation for amd64
by Alex Tarkovsky 12 Oct '07

12 Oct '07

Fixes compilation on amd64; thanks to Spencer for guidance. Also corrected bad whitespace. -- Alex Tarkovsky

3 3

darcs patch: Tabbed: don't use restackWindows
by Karsten Schoelzel 12 Oct '07

12 Oct '07

Thu Oct 11 11:44:21 CEST 2007 Karsten Schoelzel <kuser(a)gmx.de> * Tabbed: don't use restackWindows This fixes a bug visible in combination with my FloatLayout: floating windows beneath the tabs although the FloatLayout layers all floating windows on top of the normal layout.

3 3