- xmonad - Haskell.org

XMonad can't support _NET_ACTIVE_WINDOW" root window property.
by Andy Stewart 01 Dec '08

01 Dec '08

Hi, develop team! I have use XMonad some month. It's great, thanks! But i found XMonad does not support the necessary root window property, namely "_NET_ACTIVE_WINDOW". Because i have a emacs extension for SCIM-Bridge need use this root window property to compute input focus position. And can use command "xprop -root _NET_ACTIVE_WINDOW" to test this problem, will got "_NET_ACTIVE_WINDOW: no such atom on any window." message. But in GNOME, this command will get value of "_NET_ACTIVE_WINDOW". So please add this root window property in XMonad. Thanks! -- Andy.

2 2

Issue 61 in xmonad: XPrompt Ctrl+keys don't work with NumLock
by codesite-noreply＠google.com 01 Dec '08

01 Dec '08

Comment #3 on issue 61 by lit...(a)hethrael.org: XPrompt Ctrl+keys don't work with NumLock http://code.google.com/p/xmonad/issues/detail?id=61 This issue has been fixed and can be closed. -- 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

Floating-layer oddity when raising
by Mike Lundy 30 Nov '08

30 Nov '08

I'm seeing a oddity with floating windows and WindowGo.raise. When I focus a floating window and trigger a cross-workspace raise operation, I get a weird flipping behavior where it switches between the workspace I was on and the workspace I was switching to in an infinite loop. It doesn't happen every time with every floating window- there's some factor there I'm not seeing. If I float an xterm and try to reproduce it, it only happens sometimes (it's bursty, though, and I'm not sure what causes it to happen). gwern@freenode said he reproduced it with mnemosyne, and we both reproduced it with twitux (a twitter client). For me, I can trigger it with twitux 100% of the time. Procedure: 1) Launch twitux 2) Connect (you need a twitter account, unfortunately) 3) Hit Ctrl-N to pop up the "new message" dialog 4) Click into the new message text box in the float (without this, it doesn't break for me) 5) Trigger a cross-workspace raise. Boom. (The easiest way I've found to break the loop once it happens is to to a manual workspace move) Let me know if I can help further.

3 2

Floating Workspace: How Resize Windows
by Dominik Bruhn 30 Nov '08

30 Nov '08

Hy, on a workspace using the "Simple Float" Layout, how can I resize a window? as soon as I use the Mod4+right-mouse-buttom click the doesnt get managed by the "Simple Float" Layout but by the internal floating layout. Anyway: Are there any plans to implement a working floating-support? Using Applications Like Gimp or Inkscape is nearly impossible using xmonad. Greetings -- Dominik Bruhn mailto: dominik(a)dbruhn.de

3 2

Issue 242 in xmonad: inter screen handling doesn't work with xrandr --right-of, works with --left-of
by codesite-noreply＠google.com 29 Nov '08

29 Nov '08

Status: New Owner: ---- New issue 242 by ddbremner: inter screen handling doesn't work with xrandr --right-of, works with --left-of http://code.google.com/p/xmonad/issues/detail?id=242 What steps will reproduce the problem? 1. log into to my thinkpad X61 with external monitor attached 2. xrandr --output VGA --right-of LVDS --mode 1280x1024 3. mod-shift-e in a client on the external screen What is the expected output? What do you see instead? the client should go to the laptop screen instead, it disappears (although it still shows in the kicker list) What version of the product are you using? On what operating system? xmonad 0.8 on debian. I tried with the unstable and experimental versions of the Xserver Please provide any additional information below. If I instead run xrandr --output VGA --left-of LVDS, things work as expected. If I run --right-of _after_ --left-of, it seems to work as well. If this error is due to a module from XMonadContrib, please tag this issue with 'Component-Contrib' below. -- 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 234 in xmonad: broken links in xmonad contrib docs
by codesite-noreply＠google.com 29 Nov '08

29 Nov '08

Comment #5 on issue 234 by roma(a)ro-che.info: broken links in xmonad contrib docs http://code.google.com/p/xmonad/issues/detail?id=234 David has applied my patch which fixes the issue. Now somebody has to rebuild docs for website with darcs haddock. -- 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

darcs patch: Correctly implement section 4.1.7 of ICCCM
by Roman Cheplyaka 26 Nov '08

26 Nov '08

Mon Nov 24 20:46:32 EET 2008 Roman Cheplyaka <roma(a)ro-che.info> * Correctly implement section 4.1.7 of ICCCM Based on patch and investigation by Ivan Tarasov. Fixes #177. - do setInputFocus iff 'input' field of WM_HINTS is True - send WM_TAKE_FOCUS if needed

3 7

Issue 200 in xmonad: xmonad spins in a tight loop changing focus back and forth
by codesite-noreply＠google.com 26 Nov '08

26 Nov '08

Comment #6 on issue 200 by lucia.culakova: xmonad spins in a tight loop changing focus back and forth http://code.google.com/p/xmonad/issues/detail?id=200 I have observed a very similar effect, and the cause was use of XMonad.Actions.Warp with recent xmonad (0.8 for sure, maybe even 0.7?). Changing to use XMonad.Action.UpdateMouse fixed the problem for me, or so it seems. -- 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 241 in xmonad: 0.8: moving floated window changes the current tiled master
by codesite-noreply＠google.com 25 Nov '08

25 Nov '08

Comment #3 on issue 241 by lucia.culakova: 0.8: moving floated window changes the current tiled master http://code.google.com/p/xmonad/issues/detail?id=241 Ah, indeed, it is fixed now. "Just after" might be an overstatement, since I have encountered this bug a while ago and tried to update do darcs without any improvement. However, there is now a different bug, after pulling the 2 patches I have excluded: Wed May 21 23:50:57 CEST 2008 Trevor Elliott <trevor(a)galois.com> * Raise windows in the floating layer when moving or resizing Thu Sep 11 07:39:09 CEST 2008 Devin Mullins <me(a)twifkak.com> * add W.shiftMaster, fix float/tile-reordering bug When I drag a tiled window that is not master, it *first* jumps to master position and size and then moves, which is... counterintuitive, at best. Might be worth filing a new report, then? -- 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 241 in xmonad: 0.8: moving floated window changes the current tiled master
by codesite-noreply＠google.com 25 Nov '08

25 Nov '08

Comment #2 on issue 241 by jus...(a)justinbogner.com: 0.8: moving floated window changes the current tiled master http://code.google.com/p/xmonad/issues/detail?id=241 This was fixed in darcs right after the 0.8 release. As a workaround, you could rebind your mouse buttons to not use windows W.swapMaster. -- 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