MultiToggle FULL crashes my WM

Hi all, The following configuration crashes my xmonad consistently after switching layouts twice. I'd really like to be able to maximize/unmaximize the focused window and this seemed like the best way to do it. If MultiToggle isn't the right solution, I'm open to suggestions. thanks ... -deech -- myLayout = mkToggle1 FULL $ simpleTabbed ||| tiled ||| Mirror tiled ||| Circle -- where -- -- default tiling algorithm partitions the screen into two panes -- tiled = Tall nmaster delta ratio -- -- The default number of windows in the master pane -- nmaster = 1 -- -- Default proportion of screen occupied by master pane -- ratio = 1/2 -- -- Percent of screen to increment by when resizing panes -- delta = 3/100 -- main = xmonad $ -- defaultConfig { layoutHook = myLayout }

On Thu, Aug 27, 2009 at 09:00:53PM +0200, Nils wrote:
I myself use toggleLayouts, but its definitly "Full", not "FULL". ;)
Oh snap. Typical think-before-post. :) Did you import both, "XMonad.Layout.MultiToggle" *and* "XMonad.Layout.MultiToggle.Instances"? I can't see any other mistakes tho, your code works fine here.

On Thu, Aug 27, 2009 at 01:35:06PM -0500, aditya siram wrote:
Hi all, The following configuration crashes my xmonad consistently after switching layouts twice. I'd really like to be able to maximize/unmaximize the focused window and this seemed like the best way to do it. If MultiToggle isn't the right solution, I'm open to suggestions.
thanks ... -deech
-- myLayout = mkToggle1 FULL $ simpleTabbed ||| tiled ||| Mirror tiled ||| Circle -- where -- -- default tiling algorithm partitions the screen into two panes -- tiled = Tall nmaster delta ratio -- -- The default number of windows in the master pane -- nmaster = 1 -- -- Default proportion of screen occupied by master pane -- ratio = 1/2 -- -- Percent of screen to increment by when resizing panes -- delta = 3/100
-- main = xmonad $ -- defaultConfig { layoutHook = myLayout }
Known bug with toggle interfering with tabbed's state: http://code.google.com/p/xmonad/issues/detail?id=189 The bug is pretty bad, but apparently we haven't been able to convince the maintainer to fix it. Cheers, Spencer Janssen
participants (3)
-
aditya siram
-
Nils
-
Spencer Janssen