May 2008 - xmonad - Haskell.org

Issue 187 in xmonad: UpdatePointer moves pointer unnecessary
by codesite-noreply＠google.com 11 May '08

11 May '08

Issue 187: UpdatePointer moves pointer unnecessary http://code.google.com/p/xmonad/issues/detail?id=187 Comment #3 by robr...(a)bobturf.org: I'm not really sure why the w == w' wasn't working correctly. For me at least it seems to fail only for some windows with no real pattern on which windows will be affected. Anyway, the attached patch replaces the window equality with region checking and it seems to work more reliably. Please test and report. Attachments: pointer.patch 12.1 KB -- 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

Possilbe Bug: Wrong frame got focus when switching workspaces
by Dominik Bruhn 10 May '08

10 May '08

Hy, im not sure if this is a bug, a configuration issue or nothing of this: How to reproduce: 1. Get a "Tall" Layout on one workspace (say workspace 1) and open at least two windows. 2. Move the mouse over on of the Windows on the first workspace (take the left one). Let the pointer stay there. 3. Switch to another workspace. 4. Move the pointer to the right so that it will be over the second window (the right one) if you switch back 5. Switch back to the first workspace. What is expected: The right window should be focused. What happens: The left window still has the focus as long as you dont move the mouse out of the right window and into it again the focus stays on the left window. Does anybody understand what I want to tell? Thanks anyway. -- Dominik Bruhn mailto: dominik(a)dbruhn.de

2 1

keynav: mouseless X11 navigation
by Don Stewart 09 May '08

09 May '08

Spencer found this, and a few of the devs are trying it out now: "keynav is geared towards selecting a piece of the screen very quickly." "You select a piece of the screen. The screen is initially wholely selected. One move will cut that region by half. A move is a direction: up, down, left, and right. Once you're done moving, you simply indicate (with a key stroke) that you want to move. Boom, cursor moves." http://www.semicomplete.com/projects/keynav/ Works well with xmonad, and might obviate yet further the need for a mouse. Try it out, and let us know what people think. -- Don

2 1

[patch] xmobar function added to DynamicLog
by veselov＠gmail.com 08 May '08

08 May '08

Hi all! I've added 'xmobar' function to DynamicLog, which runs xmobar with some default settings. It works similar to 'dzen' function and can be used as: main = xmobar xmonad I hope this might be useful. -- WBR, Ivan N. Veselov aka sphynx.

2 1

darcs patch: HintedTile: Improve documentation.
by lithis 08 May '08

08 May '08

Improved documentation for HintedTile.

3 3

Issue 188 in xmonad: Changing focus from a dialog box in openoffice causes 100% cpu usage
by codesite-noreply＠google.com 07 May '08

07 May '08

Issue 188: Changing focus from a dialog box in openoffice causes 100% cpu usage http://code.google.com/p/xmonad/issues/detail?id=188 Comment #1 by lit...(a)hethrael.org: I also have this problem. I am currently running Ubuntu Hardy (OpenOffice 2.4.0, GHC 6.8.2) with xmonad darcs and X11 1.4.2 compiled manually. This also occurred with Ubuntu Gutsy (OpenOffice 2.3.0, GHC 6.6.1) with xmonad darcs and X11 1.4.2. This has happened for quite a while, so it’s not a recent bug in xmonad. I set OOO_FORCE_DESKTOP to gnome and run gnome-settings-daemon from my .xsession. Unsetting OOO_FORCE_DESKTOP fixes the problem for me. obrien654j does not have OOO_FORCE_DESKTOP set, though. -- 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 188 in xmonad: Changing focus from a dialog box in openoffice causes 100% cpu usage
by codesite-noreply＠google.com 07 May '08

07 May '08

Issue 188: Changing focus from a dialog box in openoffice causes 100% cpu usage http://code.google.com/p/xmonad/issues/detail?id=188 New issue report by obrien654j: What steps will reproduce the problem? 1. Open openoffice.org 2. Go to Insert->Table 3. Move mouse away from dialog box 4. Watch cpu usage skyrocket and system become unusable. What version of the product are you using? On what operating system? #uname -a Linux newo 2.6.24-ARCH #1 SMP PREEMPT Sun Mar 30 11:40:06 CEST 2008 i686 Intel(R) Pentium(R) M processor 1400MHz GenuineIntel GNU/Linux openoffice-base 2.4.0-2 ghc 6.8.2-1 java version "1.6.0_05" Java(TM) SE Runtime Environment (build 1.6.0_05-b13) Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode, sharing) Running xmonad-darcs and xmonad-contrib-darcs, manually installed. 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

Issue 120 in xmonad: Determine numlockMask automatically
by codesite-noreply＠google.com 07 May '08

07 May '08

Issue 120: Determine numlockMask automatically http://code.google.com/p/xmonad/issues/detail?id=120 Comment #5 by allbery.b: But does it use a modifier? Mine doesn't seem to, it's implemented at a different level than that. Start X11.app and run "xmodmap -pm" in the initial xterm --- I think you'll find there is no NumLock mapping (and that mod2 is Cmd aka Meta, unless you've changed settings). BTW, the fact that NumLock isn't given its own modifier slot like control, shift, and lock is indicative of how common a dedicated numlock was when X11 was developed. -- 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 187 in xmonad: UpdatePointer moves pointer unnecessary
by codesite-noreply＠google.com 07 May '08

07 May '08

Issue 187: UpdatePointer moves pointer unnecessary http://code.google.com/p/xmonad/issues/detail?id=187 Comment #2 by nomeata: On two workspaces, open one window (which then covers the whole screen). Configure UpdatePointer to move the pointer to a relative position, e.g. Relative 0.8 0.8. Move the pointer to the middle of the window, and switch to the other one. The pointer moves to the configured relative position, although it is not necessary, as it already hovers the current window. -- 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 120 in xmonad: Determine numlockMask automatically
by codesite-noreply＠google.com 07 May '08

07 May '08

Issue 120: Determine numlockMask automatically http://code.google.com/p/xmonad/issues/detail?id=120 Comment #4 by YitzGale: > Keep in mind that NumLock is a PC-ism; Macs don't have it > (and mod2 defaults to being the Cmd key in X11.app) My MacBook has a NumLock key. I don't know if it's mod2 though. I don't run xmonad on the Mac. -- 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