- xmonad - Haskell.org

Slow reload
by Yitzchak Gale 28 Apr '08

28 Apr '08

When xmonad needs to recompile xmonad.hs during a reload, that can take time. My machine is a little slow, and sometimes it can be under load. Really weird things can happen In that situation. xmonad seems to be in limbo while the compilation is happening, before the red border flashes. So, for example, let's say I press mod-Q again during that time. I'm using KDE, with Windows as my xmonad mod key. With xmonad in limbo, KDE gets the key press. If the current window happens to be a Konsole, for example, that causes the mod key to stop working even after the xmonad reload finishes. Very embarrassing! Seems to me that xmonad ought to do the following on reload: 1. Pop up a floater that says "xmonad reloading..." 2. Compile the config module in the background. Meanwhile, keep catching xmonad key events but ignore them. 3. When the compilation finishes, dismiss the floater and restart with the new config. Is this possible? Besides key presses, other interesting things can happen during a reload. There are probably numerous race conditions lurking here. Thanks, Yitz

4 5

Issue 184 in xmonad: Recompile in background
by codesite-noreply＠google.com 27 Apr '08

27 Apr '08

Issue 184: Recompile in background http://code.google.com/p/xmonad/issues/detail?id=184 New issue report by YitzGale: If recompiling xmonad.hs takes time during a reload, xmonad enters a suspended state. There is no immediate feedback from the mod-Q keypress. This may also be causing serious race conditions, as discussed in the following thread: http://www.haskell.org/pipermail/xmonad/2008-April/005545.html Therefore, I suggest that xmonad should recompile xmonad.hs in the background, while staying active, and only actually reload after the compilation is complete. In addition, there should be immediate feedback to indicate that a recompile/reload is in progress, in addition to the "flashing red border" when the reload is complete. Issue attributes: Status: New Owner: ---- Labels: Type-Defect Priority-Medium -- 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

A NAME anchors on web page please
by Yitzchak Gale 27 Apr '08

27 Apr '08

Could we please have some <A NAME=...> anchors on the main xmonad web page so that we can link to specific sections there? I need "ports and distributions" at the moment, but I think it would make sense to have anchors for every <Hn> section. Thanks, Yitz

2 2

Issue 183 in xmonad: "Choose" layout combinator is not associative
by codesite-noreply＠google.com 27 Apr '08

27 Apr '08

Issue 183: "Choose" layout combinator is not associative http://code.google.com/p/xmonad/issues/detail?id=183 New issue report by r...(a)ro-che.info: What steps will reproduce the problem? Set layoutHook to (a|||b)|||c for some atomic layouts a,b,c. What is the expected output? What do you see instead? It's expected that all three layouts are choosable using NextLayout message. However, only a and c are choosable. It's because code which works with Choose data type expects the tree to grow to the left. Note, that while this can be fixed in place, there's NewSelect layout combinator in XMonad.Layout.LayoutCombinators, which has wider functionality and doesn't have this bug. So I find it's a good time to merge it into the core. Issue attributes: Status: Accepted Owner: r...(a)ro-che.info Labels: Type-Defect Priority-Medium Component-Core -- 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

Grid layout eats other layouts
by Yitzchak Gale 27 Apr '08

27 Apr '08

Using xmonad 0.7 and KDE 3.5 with the xmonad.hs from http://haskell.org/haskellwiki/Xmonad/Using_xmonad_in_KDE I want to add Grid to the default list of layouts. When I do: 3a4 > import XMonad.Layout.Grid 10c11 < , layoutHook = avoidStruts $ layoutHook defaultConfig --- > , layoutHook = avoidStruts $ layoutHook defaultConfig ||| Grid I only get Tall and Grid. The last two layouts from defaultConfig - Mirror Tall and Full - disappear, seemingly "eaten" by Grid. If I specify the entire layout list manually: 3a4 > import XMonad.Layout.Grid 10c11,12 < , layoutHook = avoidStruts $ layoutHook defaultConfig --- > , layoutHook = avoidStruts $ let t = Tall 1 (3/100) (1/2) in > t ||| Mirror t ||| Full ||| Grid I get all four layouts as expected. Any ideas why? Thanks, Yitz

3 6

darcs patch: Error fix for Tabbed when tabbar always shown
by ivan.miljenovic＠gmail.com 25 Apr '08

25 Apr '08

Thu Apr 24 16:31:35 EST 2008 Ivan.Miljenovic(a)gmail.com * Error fix for Tabbed when tabbar always shown

3 2

Issue 178 in xmonad: UpdatePointer behavior not usable with Tabbed layout
by codesite-noreply＠google.com 22 Apr '08

22 Apr '08

Issue 178: UpdatePointer behavior not usable with Tabbed layout http://code.google.com/p/xmonad/issues/detail?id=178 Comment #9 by laylward: It works perfectly now, thanks! Attachments: 0 bytes -- 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 178 in xmonad: UpdatePointer behavior not usable with Tabbed layout
by codesite-noreply＠google.com 22 Apr '08

22 Apr '08

Issue 178: UpdatePointer behavior not usable with Tabbed layout http://code.google.com/p/xmonad/issues/detail?id=178 Comment #8 by Klaus.Weidner: re comment #7: thanks for reporting that, there was a mistake in the issue #180 comment #5 patch. Please try the latest core patch in issue #180 instead. I've done a full clean-and-recompile sequence and it works for me now. -- 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 180 in xmonad: In focus-follows-mouse mode, the wrong window gets focused
by codesite-noreply＠google.com 22 Apr '08

22 Apr '08

Issue 180: In focus-follows-mouse mode, the wrong window gets focused http://code.google.com/p/xmonad/issues/detail?id=180 Comment #6 by Klaus.Weidner: My previous core patch was incorrect as reported in issue #178, the mouseFocused was unconditionally set to True which disabled UpdatePointer. Please try this updated patch instead. I apologize for the inconvenience. Attaching the contrib patch also for completeness, that one is unchanged. Attachments: xmonad-core-mouse-focused.dpatch 3.4 KB xmonad-contrib-mouse-focused.dpatch 7.2 KB -- 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 178 in xmonad: UpdatePointer behavior not usable with Tabbed layout
by codesite-noreply＠google.com 22 Apr '08

22 Apr '08

Issue 178: UpdatePointer behavior not usable with Tabbed layout http://code.google.com/p/xmonad/issues/detail?id=178 Comment #7 by laylward: After a full recompile/restart it does not seem to be updating the mouse position most of the time. The only case I can get it to jump is by clicking a link in one window that makes firefox take focus. None of the keyboard focus controls seem to trigger a mouse position update. -- 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