- xmonad - Haskell.org

Issue 71 in xmonad: Problems with initial size of floating windows
by codesite-noreply＠google.com 08 Dec '07

08 Dec '07

Issue 71: Problems with initial size of floating windows http://code.google.com/p/xmonad/issues/detail?id=71 Comment #1 by SpencerJanssen: Fixed. Issue attribute updates: Status: 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 75 in xmonad: float mode and automatic workspace placement don't work together
by codesite-noreply＠google.com 08 Dec '07

08 Dec '07

Issue 75: float mode and automatic workspace placement don't work together http://code.google.com/p/xmonad/issues/detail?id=75 Comment #2 by SpencerJanssen: (No comment was entered for this change.) Issue attribute updates: Status: 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 75 in xmonad: float mode and automatic workspace placement don't work together
by codesite-noreply＠google.com 08 Dec '07

08 Dec '07

Issue 75: float mode and automatic workspace placement don't work together http://code.google.com/p/xmonad/issues/detail?id=75 Comment #1 by SpencerJanssen: Fixed in 0.5 -- 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 74 in xmonad: cinellera does not launch (normally)
by codesite-noreply＠google.com 08 Dec '07

08 Dec '07

Issue 74: cinellera does not launch (normally) http://code.google.com/p/xmonad/issues/detail?id=74 Comment #1 by SpencerJanssen: I believe this is a cinelerra bug, WontFix until demonstrated otherwise. 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

1 0

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

08 Dec '07

Issue 54: Composable manageHooks interface http://code.google.com/p/xmonad/issues/detail?id=54 Comment #6 by SpencerJanssen: (No comment was entered for this change.) Issue attribute updates: Status: 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 54 in xmonad: Composable manageHooks interface
by codesite-noreply＠google.com 08 Dec '07

08 Dec '07

Issue 54: Composable manageHooks interface http://code.google.com/p/xmonad/issues/detail?id=54 Comment #5 by SpencerJanssen: Done in 0.5, see XMonad.ManageHooks. -- 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 46 in xmonad: xmonad's output (logHook) needs to be separated from output from client programs
by codesite-noreply＠google.com 08 Dec '07

08 Dec '07

Issue 46: xmonad's output (logHook) needs to be separated from output from client programs http://code.google.com/p/xmonad/issues/detail?id=46 Comment #3 by SpencerJanssen: (No comment was entered for this change.) Issue attribute updates: Status: 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 46 in xmonad: xmonad's output (logHook) needs to be separated from output from client programs
by codesite-noreply＠google.com 08 Dec '07

08 Dec '07

Issue 46: xmonad's output (logHook) needs to be separated from output from client programs http://code.google.com/p/xmonad/issues/detail?id=46 Comment #2 by SpencerJanssen: This is fixed for 0.5, see spawnPipe et al -- 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 47 in xmonad: Allow selection of the floating layout in Config.hs
by codesite-noreply＠google.com 08 Dec '07

08 Dec '07

Issue 47: Allow selection of the floating layout in Config.hs http://code.google.com/p/xmonad/issues/detail?id=47 Comment #1 by SpencerJanssen: (No comment was entered for this change.) Issue attribute updates: Labels: -Type-Defect Type-Enhancement -- 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 97 in xmonad: xmonad stops responding to keyboard input after running xscreensaver
by codesite-noreply＠google.com 07 Dec '07

07 Dec '07

Issue 97: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 Comment #1 by byorgey: Another data point: today, after unlocking the screen, neither the mouse nor the keyboard would respond. I was still able to switch to a virtual terminal and log in, so I could verify that xmonad was still running. I decided to kill xscreensaver, and it caused X to exit as well. At this point I have no idea whether this is an xmonad bug or an xscreensaver bug. -- 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