February 2009 - xmonad

darcs patch: X.L.Mosaic: prevent users from causing n... (and 2 more)
by Adam Vogt 18 Feb '09

18 Feb '09

Mon Feb 9 21:27:27 EST 2009 Adam Vogt <vogt.adam(a)gmail.com> * X.L.Mosaic: prevent users from causing non-termination with negative elements Wed Feb 18 16:33:11 EST 2009 Adam Vogt <vogt.adam(a)gmail.com> * small cleanup in X.L.Mosaic Wed Feb 18 17:32:22 EST 2009 Adam Vogt <vogt.adam(a)gmail.com> * add Tabify layout modifier Allows arbitrary windows to be combined into tabs groups. The group focus follows the StackSet focus, and groups can be combined with a simple message. Currently the Merge message's parameters can only be provided by a new WindowNavigation message (Apply).

1 1

darcs patch: X.L.Mosaic: prevent users from causing n... (and 2 more)
by Adam Vogt 18 Feb '09

18 Feb '09

Mon Feb 9 21:27:27 EST 2009 Adam Vogt <vogt.adam(a)gmail.com> * X.L.Mosaic: prevent users from causing non-termination with negative elements Wed Feb 18 16:33:11 EST 2009 Adam Vogt <vogt.adam(a)gmail.com> * small cleanup in X.L.Mosaic Wed Feb 18 17:44:31 EST 2009 Adam Vogt <vogt.adam(a)gmail.com> * Add TabbedModifier layout modifer Allows arbitrary windows to be combined into tabs groups. The group focus follows the StackSet focus, and groups can be combined with a simple message. Currently the Merge message's parameters can only be provided by a new WindowNavigation message (Apply).

1 0

complexity of 'windows'
by lowly coder 17 Feb '09

17 Feb '09

I'm looking at the 'windows' function, and do not understand why it's so complicated. If it's just WindowSet -> WindowSet ... why is it so long? I ask this because I want to manipulate the WindowSet of a workspace that is _NOT_ visible; the only function that is WindowSet -> WindowSet is "windows". However, windows has W.current hard coded into it -- and I'm not sure what all of the other stuff in there is.

4 4

sending window to invisible workspace?
by lowly coder 17 Feb '09

17 Feb '09

I have the following in xmonad.hs: myWorkspaces = ["0", "1", "2"] ... [((m .|. mod4Mask, key), screenWorkspace sc >>= flip whenJust (windows . f)) | (key, sc) <- zip [xK_y, xK_u, xK_i] [0..] , (f, m) <- [(W.shift, 0), (W.shift, shiftMask)]] now, I'm also using screenLayout, giving me two 'workspaces' on a single screen mod4-y & mod4-u work when I have two workspcaes visible, but mod4-i does not when I only have one workspace visbile, mod4-u and mod4-i both do not work is there some rule saying "you can only send windows to visible workspaces" ? thanks!

2 1

odd interaction between xmonad and tsclient
by David Cabana 17 Feb '09

17 Feb '09

I sometimes use tsclient/rdesktop to connect to a Windows box. I find that once focus is inside the remote Windows desktop, any xmonad command depending on the use of the mode key (the Windows key, in my case) fails. The key press of the Windows key seems to go to the remote Windows box rather than to the local X system. I say this because pressing the Windows key immediately pops up the Windows start menu. I happen to run the gnome panel with a workspace switcher, and so can use it and the mouse to break out of the remote Windows session, but that seems inelegant. Has anyone else encountered this problem, or have a solution for it? Thank you, drc

2 1

keyboard fun
by lowly coder 16 Feb '09

16 Feb '09

in my .xmonad/xmonad.hs , I have: ++ [((m .|. mod4Mask, key), screenWorkspace sc >>= flip whenJust (windows . f)) | (key, sc) <- zip [xK_a, xK_f] [0..] , (f, m) <- [(W.view, 0)]] ++ [((m .|. mod4Mask, key), screenWorkspace sc >>= flip whenJust (windows . f)) | (key, sc) <- zip [xK_s, xK_d] [0..] , (f, m) <- [(W.shift, 0)]] now, instead of this, I'd perfer to have something where xK_f alternates between workspace 0 & 1 I'd also like to make xK_d to send current window to other workspace (this requires that I somehow know what my current workspace is -- is there a function to return this?)

2 5

Issue 228 in xmonad: Fullscreen windows are tiled
by codesite-noreply＠google.com 16 Feb '09

16 Feb '09

Updates: Status: WontFix Comment #8 on issue 228 by dons00: Fullscreen windows are tiled http://code.google.com/p/xmonad/issues/detail?id=228 Closing. not a bug. These are just tiled windows. Whether they should float by default is a different feature request. -- 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 275 in xmonad: XMonad.Contrib.Loggers.battery creates zombie sh if acpi not installed
by codesite-noreply＠google.com 16 Feb '09

16 Feb '09

Comment #3 on issue 275 by dyfrgi: XMonad.Contrib.Loggers.battery creates zombie sh if acpi not installed http://code.google.com/p/xmonad/issues/detail?id=275 Apoligies; I forgot to comment about this after it was fixed during discussion on IRC. Agreed - this problem is absent in darcs. -- 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 275 in xmonad: XMonad.Contrib.Loggers.battery creates zombie sh if acpi not installed
by codesite-noreply＠google.com 16 Feb '09

16 Feb '09

Updates: Status: Invalid Comment #2 on issue 275 by roma(a)ro-che.info: XMonad.Contrib.Loggers.battery creates zombie sh if acpi not installed http://code.google.com/p/xmonad/issues/detail?id=275 This problem is absent in darcs. -- 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 275 in xmonad: XMonad.Contrib.Loggers.battery creates zombie sh if acpi not installed
by codesite-noreply＠google.com 16 Feb '09

16 Feb '09

Comment #1 on issue 275 by dyfrgi: XMonad.Contrib.Loggers.battery creates zombie sh if acpi not installed http://code.google.com/p/xmonad/issues/detail?id=275 Component-Contrib -- 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