- xmonad - Haskell.org

darcs patch: Util.Run: minor clarification in comment
by gwern0＠gmail.com 03 Mar '08

03 Mar '08

Mon Mar 3 00:15:13 EST 2008 gwern0(a)gmail.com * Util.Run: minor clarification in comment

2 1

new contrib module: XMonad.Actions.PerWorkspaceKeys
by Roman Cheplyaka 02 Mar '08

02 Mar '08

It allows to define different keybindings for different workspaces. Enjoy :) -- Roman I. Cheplyaka (aka Feuerbach @ IRC)

1 0

darcs patch: Haddock fix: Changed URL-Markup
by Dominik Bruhn 02 Mar '08

02 Mar '08

2 1

Proposal: Advanced Scratchpad-Features
by Dominik Bruhn 29 Feb '08

29 Feb '08

Hy, I recently found the Scratchpad on the Mailinglist (thanks, Braden for this). But, im missing two features: 1. Is it possible to hide the scratchpad (not close, only hide) with the same hotkey? So if I press the Hotkey once the scratchpad apears and another hit it disapears and I can recall it with the same hotkey. 2. Can the scratchpad made visible on all workspaces? So if I switch my workspace it stays visilbe and I can recall (with 1.) the same scratchpad everywhere? The reason for this is: I want to start a musicplayer (mocp or something like this) in the scratchpad and want to view it on every workspace im on. Is this possible? Thanks -- Dominik Bruhn mailto: dominik(a)dbruhn.de

7 8

Issue 143 in xmonad: XEvent hook or similar needed
by codesite-noreply＠google.com 29 Feb '08

29 Feb '08

Issue 143: XEvent hook or similar needed http://code.google.com/p/xmonad/issues/detail?id=143 Comment #10 by Braden.Shepherdson: Part of the question is speed; if every event gets run through a list of such handlers, it seems like the majority of the events will end up back in the hands of Main's handle function. I don't know how frequently events arrive. Maybe use pattern matching? Rename the existing handle to handle', the new handle tries the user's messageHook (:: Event -> X Bool, pattern matching like handle but indicating whether handle' should still process the event), and if the response is False, try it with handle'. I'm not sure how pattern matching would compare speed-wise with a list. It also enforces only one handler per event, which I think might be desirable. Whatever solution is settled on, I think it's desirable to have type -> X Bool, so the user's message handlers can either eat the event, or leave it to be processed as normal. That opens up the ability for extensions to observe events without consuming them. And as a use case other than EWMH: timers. The current Util.Timer module only works for LayoutModifiers, because only they can handleMessage right now. Instead, this module could just offer a handleTimer to use in messageHook, and then we have general-purpose timers. -- 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 57 in xmonad: Amarok OSD goes missing
by codesite-noreply＠google.com 29 Feb '08

29 Feb '08

Issue 57: Amarok OSD goes missing http://code.google.com/p/xmonad/issues/detail?id=57 Comment #2 by spo...(a)cs.cmu.edu: According to xprop, the Amarok OSD has _NET_WM_STATE(ATOM) = _NET_WM_STATE_ABOVE, _NET_WM_STATE_STAYS_ON_TOP WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING Does XMonad support extended hints like ABOVE? FWIW, I've also seen a similar behavior when using KDE's Katapult (http://katapult.kde.org/) with XMonad. -- 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 124 in xmonad: Closing windows while reloading configuration confuses xmonad
by codesite-noreply＠google.com 29 Feb '08

29 Feb '08

Issue 124: Closing windows while reloading configuration confuses xmonad http://code.google.com/p/xmonad/issues/detail?id=124 Comment #3 by SpencerJanssen: Fixed a few weeks back. 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 57 in xmonad: Amarok OSD goes missing
by codesite-noreply＠google.com 29 Feb '08

29 Feb '08

Issue 57: Amarok OSD goes missing http://code.google.com/p/xmonad/issues/detail?id=57 Comment #1 by SpencerJanssen: Amarok ought to raise the OSD when necessary -- not an xmonad bug IMO. Issue attribute updates: Status: Invalid -- 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 121 in xmonad: java/firefox gray box
by codesite-noreply＠google.com 29 Feb '08

29 Feb '08

Issue 121: java/firefox gray box http://code.google.com/p/xmonad/issues/detail?id=121 Comment #2 by SpencerJanssen: More Java bugs. Hopefully the submitter found a solution. Issue attribute updates: Status: Invalid -- 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 107 in xmonad: Floating windows cause combo-boxes and other widgets in applications to faill.
by codesite-noreply＠google.com 29 Feb '08

29 Feb '08

Issue 107: Floating windows cause combo-boxes and other widgets in applications to faill. http://code.google.com/p/xmonad/issues/detail?id=107 Comment #3 by SpencerJanssen: Not enough information to move on this. 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