- xmonad - Haskell.org

darcs patch: export constructor to make ThreeColumns layout usable ...
by Daniel Neri 03 Oct '07

03 Oct '07

Wed Oct 3 11:31:03 CEST 2007 Daniel Neri <daniel.neri(a)sigicom.se> * export constructor to make ThreeColumns layout usable again

2 1

darcs patch: Make extra WindowNavigation borders configurable
by Jamie Webb 03 Oct '07

03 Oct '07

Personally I find the new highlighting feature more distracting than useful, so this patch adds a parameter to enable/disable it. /J Wed Oct 3 02:07:46 BST 2007 Jamie Webb * Make extra WindowNavigation borders configurable

3 2

darcs patch: SwapWorkspaces for XMonadContrib
by Devin Mullins 03 Oct '07

03 Oct '07

Ermm.... having personal problems with my Postfix/ISP setup, so I'm hand sending this. Hopefully it's no prob. sometime today me * SwapWorkspaces, so you can move the workspaces around without having to rewire the number keys on your keyboard.

2 1

darcs patch: Layout -> LayoutClass for ResizableTile and MosaicAlt
by Jamie Webb 03 Oct '07

03 Oct '07

Wed Oct 3 02:08:49 BST 2007 Jamie Webb * Layout -> LayoutClass for ResizableTile and MosaicAlt

2 1

Issue 50 in xmonad: OS X + unclutter == rare "focus lock"
by codesite-noreply＠google.com 03 Oct '07

03 Oct '07

Issue 50: OS X + unclutter == rare "focus lock" http://code.google.com/p/xmonad/issues/detail?id=50 Comment #4 by SpencerJanssen: Just change the 'Status' field. I changed it to 'Duplicate' since we've seen this in bug #45 Issue attribute updates: Status: Duplicate -- 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 50 in xmonad: OS X + unclutter == rare "focus lock"
by codesite-noreply＠google.com 03 Oct '07

03 Oct '07

Issue 50: OS X + unclutter == rare "focus lock" http://code.google.com/p/xmonad/issues/detail?id=50 Comment #3 by m...(a)twifkak.com: How right you are. Sorry about the dupe. I don't see a 'Closed' button, but I'd press it if I did. -- 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 50 in xmonad: OS X + unclutter == rare "focus lock"
by codesite-noreply＠google.com 03 Oct '07

03 Oct '07

Issue 50: OS X + unclutter == rare "focus lock" http://code.google.com/p/xmonad/issues/detail?id=50 Comment #2 by andrea.rossato: Did you try to reproduce this issue by running unclutter with the grab option? unclutter -grab It seems to me that this report is a duplicate of this: http://code.google.com/p/xmonad/issues/detail?id=45&can=1 which is not a XMonad bug, but an unclutter's one. Andrea -- 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 50 in xmonad: OS X + unclutter == rare "focus lock"
by codesite-noreply＠google.com 03 Oct '07

03 Oct '07

Issue 50: OS X + unclutter == rare "focus lock" http://code.google.com/p/xmonad/issues/detail?id=50 Comment #1 by m...(a)twifkak.com: D'oh! I forgot to add a couple of important steps: 0. Configure xmonad with a keybinding to spawn "killall unclutter; unclutter" or have dmenu installed and keybound. 4 1/2. Without mousing, restart unclutter (as Step 4 tends to confuse it). That contrived enough? Also probably of note is that after step 4, my mouse cursor is as if the root window had focus (e.g. the cool little X instead of the xterm I beam). -- 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 50 in xmonad: OS X + unclutter == rare "focus lock"
by codesite-noreply＠google.com 03 Oct '07

03 Oct '07

Issue 50: OS X + unclutter == rare "focus lock" http://code.google.com/p/xmonad/issues/detail?id=50 New issue report by m...(a)twifkak.com: What steps will reproduce the problem? 1. Use Apple's X11 in "full screen mode," with xmonad as your WM. 2. Have two windows open, with the focus and the mouse cursor on the first. 3. Run `unclutter &`. 4. Hit Alt-Cmd-A to exit full screen mode, and again to reenter. 5. Wait for unclutter to kick in. 6. Notice that focus shifts to the second, and mod-j/k don't do jack. (Well, they try -- you can see the red box flicker.) Wiggling the mouse cursor wakes it up and all is well. This is against darcs' latest (trunk?) as of now. 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

workspace/xinerama confusion
by Andrew Sackville-West 03 Oct '07

03 Oct '07

Hi list, I am new to xmonad, but am immediately liking it (coming from wmii). I am running debian sid with xmonad 0.3. My dual-head setup is running xinerama but it doesn't seem to behave the way I would expect from the manpage and online stuff. Specifically, when I create a series of windows, xmonad treats the two screens as one very wide screen. So, for example, the first xterm is two screens/monitors wide. The second one causes the screens to split down the middle with one xterm on each screen (monitor that is). The third xterm ends up on the right hand monitor which is split in half to accomodate both xterms. I can navigate between all the windows with mod-k/j, switch windows into the master window with mod-return etc. But this all happens across the two monitors. When I switch to workspace 2 (mod-2) I get a blank screen (as there are no wondows there). switch back with mod-1, mod-shift-2 a window, mod-2 and there it is, two monitors wide. This doesn't seem to jive with what I've read -- that each screen should have its own control and be assigned a different workspace. I suspect I have not configured X properly so here is the likely pertinent portion: Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 Screen 1 "Screen1" RightOf "Screen0" InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" Option "Xinerama" "true" EndSection I will happily provide more detail if needed. What am I missing here? thanks A

3 3