October 2011 - xmonad

Issue 470 in xmonad: XMonad shows background when it need not
by codesite-noreply＠google.com 25 Dec '11

25 Dec '11

Status: New Owner: ---- New issue 470 by jyoth...@gmail.com: XMonad shows background when it need not http://code.google.com/p/xmonad/issues/detail?id=470 What steps will reproduce the problem? 1. Open two fullscreen apps in two workspaces 2. Switch between them quickly What is the expected output? What do you see instead? I expect to see the windows of the apps and no background. Instead, the background is shown first and then the window. What version of the product are you using? On what operating system? xmonad-0.9.2-2 (arch) Please provide any additional information below. This issue is the same as Issue no. 322. Apparently the issue was closed then and has reppeared sometime later.

1 2

Issue 363 in xmonad: non-positive argument error on NVidia Xinerama set
by codesite-noreply＠google.com 14 Dec '11

14 Dec '11

Status: New Owner: ---- New issue 363 by seanerussell: non-positive argument error on NVidia Xinerama set http://code.google.com/p/xmonad/issues/detail?id=363 What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? What version of the product are you using? On what operating system? Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". Please provide any additional information 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 10

Issue 412 in xmonad: Using a compositing manager shifts windows 2px to top and left
by codesite-noreply＠google.com 27 Nov '11

27 Nov '11

Status: New Owner: ---- New issue 412 by DaPatti: Using a compositing manager shifts windows 2px to top and left http://code.google.com/p/xmonad/issues/detail?id=412 What steps will reproduce the problem? 1. Start XMonad 2. Start cairo-compmgr or xcompmgr What is the expected output? What do you see instead? Instead of their normal positioning, windows are shifted to the top left a bit so that the borders on the top and left aren’t visible anymore. As soon as I kill the compositing manager, the windows are repositioned correctly. What version of the product are you using? On what operating system? XMonad 0.9.1; Arch Linux x86_64. Tried with cairo-compmgr-git and xcompmgr. Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". The only relevant part might be borderWidth = 2. I don’t use FadeInactive or things like that. No messages on xmonad --recompile. Please provide any additional information below.

1 2

Issue 455 in xmonad: xmonad munges dialogs
by codesite-noreply＠google.com 26 Nov '11

26 Nov '11

Status: New Owner: ---- New issue 455 by hramr...@gmail.com: xmonad munges dialogs http://code.google.com/p/xmonad/issues/detail?id=455 When you move a workspace containing a floating dialog from one screen to another the dialog changes size. For some reason when the dialog appears on different screen than the app was last show it is (at least sometimes) munged as well. Note that the dialog has an application specified size at the start so I don't see any reason to resize it later.

1 3

Issue 396 in xmonad: Qt (and KDE) don't display menu if not on first display
by codesite-noreply＠google.com 25 Nov '11

25 Nov '11

Status: New Owner: ---- New issue 396 by luka.stojanovic: Qt (and KDE) don't display menu if not on first display http://code.google.com/p/xmonad/issues/detail?id=396 What steps will reproduce the problem? 1. Open Qt or KDE app 2. Place it on second display 3. try opening menu or context-menu What version of the product are you using? On what operating system? Ubuntu 10.04, amd64, xmonad 0.9 Please provide any additional information below. Qt apps that I've tried: VLC, Psi KDE apps that I've tried: Krusader, Amarok, Dolphin...

1 8

Issue 480 in xmonad: xmonad merge screens when recompile and restart
by codesite-noreply＠google.com 22 Nov '11

22 Nov '11

Status: New Owner: ---- New issue 480 by argu...@gmail.com: xmonad merge screens when recompile and restart http://code.google.com/p/xmonad/issues/detail?id=480 What steps will reproduce the problem? 1. Attach external monitor on VGA port of Thinkpad T410i 2. On terminal: xrandr --output VGA --above LVDS --auto 3. Recompile and restart with mod-q What is the expected output? What do you see instead? xmonad should recompile and restart, xmobar (which is on top of VGA) should restart looking good. xmonad does recompile but when restart it merges everything on LVDS, like if my second screen were also LVDS and seems to treat my external monitor like an extension of LVDS. I just can move windows to VGA by moving the floating window. What version of the product are you using? On what operating system? xmonad 0.9.2 on Archlinux x86_64 Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". No output when "xmonad --recompile" Please provide any additional information below. It doesn't seem to happen when I use "xrandr --output VGA --right-of LVDS --auto" Attachments: xmonad.hs 14.0 KB

1 1

Issue 469 in xmonad: The --replace flag does not work
by codesite-noreply＠google.com 19 Nov '11

19 Nov '11

Status: New Owner: ---- New issue 469 by kris...@emptybox.org: The --replace flag does not work http://code.google.com/p/xmonad/issues/detail?id=469 What steps will reproduce the problem? 1. xmonad --replace What is the expected output? What do you see instead? I expect xmonad to replace the running window manager as documented in xmonad --help Usage: xmonad [OPTION] Options: --help Print this message --version Print the version number --recompile Recompile your ~/.xmonad/xmonad.hs --replace Replace the running window manager with xmonad --restart Request a running xmonad process to restart Instead the following occurs: xmonad --replace xmonad: user error (unrecognized flags) xmonad --version xmonad 0.10 (the latest version from darcs)

1 3

darcs patch: Export types to reduce haddock warnings.
by Adam Vogt 19 Nov '11

19 Nov '11

1 patch for repository code.haskell.org:/srv/code/XMonadContrib: Sat Oct 23 15:57:55 EDT 2010 Adam Vogt <vogt.adam(a)gmail.com> * Export types to reduce haddock warnings.

2 1

Re: Issue 126 in xmonad: xmonad doesn't warn when xmonad executable cannot be found
by codesite-noreply＠google.com 12 Nov '11

12 Nov '11

Updates: Summary: xmonad doesn't warn when xmonad executable cannot be found Status: Accepted Labels: Usability Comment #6 on issue 126 by vogt.adam: xmonad doesn't warn when xmonad executable cannot be found http://code.google.com/p/xmonad/issues/detail?id=126 In #xmonad today, jeffwheeler had some trouble getting his config to reload. It seems like this problem could have been avoided by adding a bit of logic to the default config: Currently M-q is bound to: spawn "xmonad --recompile && xmonad --restart" This could instead be something like: spawn $ "which xmonad && { xmonad --recompile && xmonad --restart } || " ++ "xmessage xmonad not in \$PATH: \"$PATH\"" But maybe this logic should be implemented in haskell, or is the /bin/sh syntax used here going to work everywhere? -- 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 3

Re: [xmonad] Issue 462 in xmonad: Ewmh desktop handle event doesn't correctly handle _NET_WM_DESKTOP message type
by codesite-noreply＠google.com 10 Nov '11

10 Nov '11

Comment #3 on issue 462 by punitagr...@gmail.com: Ewmh desktop handle event doesn't correctly handle _NET_WM_DESKTOP message type http://code.google.com/p/xmonad/issues/detail?id=462 Hi, Thanks for the code sample. I tried it out but it didn't fix the issue I encountered. I played with the ewmhCopyWindow function and the following version sort of makes things better - diff -rN old-XMonadContrib/XMonad/Hooks/EwmhDesktops.hs new-XMonadContrib/XMonad/Hooks/EwmhDesktops.hs 34a35 > import XMonad.Actions.CopyWindow 54c55 < , handleEventHook = handleEventHook c +++ ewmhDesktopsEventHook --- > , handleEventHook = handleEventHook c +++ > ewmhDesktopsEventHook `mappend` ewmhCopyWindow 145a147,148 > {- else if n == 0xffffffff then > windows $ W.shiftWin (W.currentTag s) w -} 148a152 > trace $ "focus"++show w 157a162,176 > ewmhCopyWindow :: Event -> X All > ewmhCopyWindow ClientMessageEvent { > ev_window = w, > ev_message_type = mt, > ev_data = 0xffffffff : _ > } = withWindowSet $ \s -> do > a_d <- getAtom "_NET_WM_DESKTOP" > when (mt == a_d) $ do > sort' <- getSortByIndex > let ws = map W.tag $ sort' $ W.workspaces s > windows $ foldr (.) id (map (copyWindow w) ws) > trace $ show w > return (All True) > ewmhCopyWindow _ = return (All True) On further searching I think what I am really after are the changes that come in with http://code.google.com/p/xmonad/issues/detail?id=430. Now if only I can understand the code and make it work with my setup.

1 1