- xmonad - Haskell.org

Issue 82 in xmonad: Gap should be on by default
by codesite-noreply＠google.com 10 Dec '07

10 Dec '07

Issue 82: Gap should be on by default http://code.google.com/p/xmonad/issues/detail?id=82 Comment #2 by dons00: Bumped. Small issue. Issue attribute updates: Labels: -Milestone-Release0.5 Milestone-Release0.6 -- 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 73 in xmonad: xmonad as a library
by codesite-noreply＠google.com 09 Dec '07

09 Dec '07

Issue 73: xmonad as a library http://code.google.com/p/xmonad/issues/detail?id=73 Comment #6 by dons00: Done! Find template xmonad.hs file here: http://haskell.org/haskellwiki/Xmonad/Config_archive/Template_Config.hs Issue attribute updates: Status: Verified -- 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 98 in xmonad: Conventional configuration strategies
by codesite-noreply＠google.com 09 Dec '07

09 Dec '07

Issue 98: Conventional configuration strategies http://code.google.com/p/xmonad/issues/detail?id=98 Comment #1 by dons00: An example from Thomas. 1 -- Sample idea of what a non-xmonad/haskell config file might look like. 2 3 -- Set the modkey. 4 modkey = mod4 5 6 myConfig = { 7 borderWidth = 3 8 terminal = "urxvt +sb ...." 9 workspaces = "A", "B", "C", "D" 10 gaps = 15 0 0 0 11 modMask = modkey 12 .... 13 } 14 15 -- Layouts 16 layouts = tiled, mirror tiled, full (noBorders) 17 18 -- Keys 19 key a (shift) Kill 20 key right (control) rotview true 21 22 -- Mouse 23 mouse 1 focusNextWindow 24 25 -- Styles 26 Style (classname=Skype | resource=skype) StartWS A, Float 27 Style (classname=XClock) Float -- 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

3 2

Issue 98 in xmonad: Conventional configuration strategies
by codesite-noreply＠google.com 09 Dec '07

09 Dec '07

Issue 98: Conventional configuration strategies http://code.google.com/p/xmonad/issues/detail?id=98 Comment #2 by thomas.adam22: Thanks Don for that... My intention behind this proposed syntax is that is is sufficiently removed from haskell for it to be generic (i.e., does not enforce Haskell's syntax on the user), but close enough for it to be haskell so that some parser can be written. If that makes sense. Someone on IRC asked what they would do to make a ""global"" key-binding without the modifier -- if one looks at line 19, then that might be represented as: key (nomod) a kill (Potentially stupid in this example, but you get the point.) Again, line 26 (which is an abstract representation of what ManageHook might become, says that: "If a window has a class of 'skype' OR (|) a resource of 'skype' then move it to the WorkSpace of 'A' and put it in the floating layer". Hopefully that helps to clarify things a little. Kindly, Thomas Adam -- 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 98 in xmonad: Conventional configuration strategies
by codesite-noreply＠google.com 09 Dec '07

09 Dec '07

Issue 98: Conventional configuration strategies http://code.google.com/p/xmonad/issues/detail?id=98 New issue report by dons00: Now we have reconfigure without recompilation, we can consider non-Haskell mechanisms for configuration (such as a simple text format, or Xresources, or environment variables). A good choice here should ease adoption -- as users can get good results without needing haskell. Issue attributes: Status: Accepted Owner: dons00 Labels: Type-Enhancement 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

darcs patch: StackSet: some haddock tuning
by Andrea Rossato 09 Dec '07

09 Dec '07

Sun Dec 9 17:15:25 CET 2007 Andrea Rossato <andrea.rossato(a)unibz.it> * StackSet: some haddock tuning

1 0

Issue 97 in xmonad: xmonad stops responding to keyboard input after running xscreensaver
by codesite-noreply＠google.com 09 Dec '07

09 Dec '07

Issue 97: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 Comment #2 by thomas.adam22: I don't think this problem is xscreensaver specific, and I would argue is a red-herring. I too find for no apparent reason that after sometime, Firefox no longer responds to keyboard focus unless it is either moved to the floating layer and retiled or a new window is opened. This will be an issue with Firefox though, and not of XMonad itself. How best to fix it (whether XMonad can send a synthetic event to Firefox or not) is still something I am pondering. -- 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 96 in xmonad: certain dialogs get dropped in gnucash
by codesite-noreply＠google.com 09 Dec '07

09 Dec '07

Issue 96: certain dialogs get dropped in gnucash http://code.google.com/p/xmonad/issues/detail?id=96 Comment #2 by thomas.adam22: I bet I know what this bug is (I'm assuming transient windows here): The window is being mapped and unmapped. If you were to use something like xscope then you might see that: a) Application sends a mapRequest. a1) Before xmonad has a chance to do that, the application asks to be put in the WithDrawn state (via a synthetic UnmapNotify event). b) The window is mapped. c) GNUCash sends a MapRequest. d) Another UnmapNotify request is sent and the window is UnMapped. e) The MapRequest from (c) is handled and a real UnMapNotify request is issued causing the window it close, never being mapped again. I'm guessing this is what's happening, but I don't run GnuCash. -- 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

xmonad, and trends in the tiling wm market
by Don Stewart 08 Dec '07

08 Dec '07

We've not much information on what's happening with tiling wms. One source of info is the debian package system's popularity contest: if a package is in debian, we get to see a snapshot of trends. Here's a little analysis of what's been happening with the tiling wms in 2007: http://galois.com/~dons/images/tiling-window-managers.png Summary: * ion continues long term decline * ratpoison was in a place to take advantage of ion controversy * wmii and dwm continue long term growth * in late 07, the two new tiling window managers, xmonad and awesome, begin eating away at ion, ratpoison and dwm users * larswm and stumpwm are static For xmonad my hope is that improved packaging, and the ease of adding extensions, to appear in this weekend's release of xmonad 0.5 will lead to further growth. Along with xmonad's technical features over the competition, I hope to see continued growth in the coming year. We're working hard at ensuring this is the best tiling wm! Our challenge is to make the cost of installing a Haskell toolchain easier, though, so its cheaper to experiment with xmonad. This comes down to improved ghc packaging on each distro. -- Don

2 3

Issue 51 in xmonad: amsn crashes when a contact tries to open a dialog
by codesite-noreply＠google.com 08 Dec '07

08 Dec '07

Issue 51: amsn crashes when a contact tries to open a dialog http://code.google.com/p/xmonad/issues/detail?id=51 Comment #1 by SpencerJanssen: As far as we know, this problem remains. However, we can't do anything without more information. Issue attribute updates: Status: WontFix -- 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

2 1