July 2014 - xmonad - Haskell.org

Issue 538 in xmonad: X.H.DynamicBars call to xrrSelectInput has no effect
by codesite-noreply＠google.com 11 Dec '14

11 Dec '14

Status: New Owner: ---- New issue 538 by johnnysp...@gmail.com: X.H.DynamicBars call to xrrSelectInput has no effect http://code.google.com/p/xmonad/issues/detail?id=538 What steps will reproduce the problem? 1. Use attached xmonad.hs (vanilla + minimal DynamicBars). 2. Turn second display off and on: xrandr --output VGA1 --off xrandr --output VGA1 --preferred --right-of LVDS1 Bonus: 3. Apply select_input_fix.dpatch, rebuild and restart xmonad. 4. Turn second display off and on. 5. Undo previous patch, apply select_input_not_fix.dpatch, rebuild and restart xmonad. 6. Turn second display off and on. What is the expected output? What do you see instead? Expected: In steps 2, 4, and 6: see "DESTROYING"/"CREATING" messages in xmonad output. Actual: Only step 4 produces the expected messages. Steps 2 and 6 produce no output. What version of the product are you using? On what operating system? xmonad 0.11 (darcs) xmonad-contrib 0.11 (darcs) xorg 1.14.0 xrandr 1.4.0 X11 (Haskell binding) 1.6.1.1 Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". "xmonad --recompile" produces no output. Please provide any additional information below. I'm expecting step 2 to work because dynStatusBarStartup calls xrrSelectInput. This apparently doesn't do what it's supposed to do for me, possibly for the same reason that step 6 doesn't work. Attachments: xmonad.hs 551 bytes select_input_fix.dpatch 2.2 KB select_input_not_fix.dpatch 2.3 KB -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 4

Issue 447 in xmonad: installation breaks copy/paste feature of vmware-tools
by codesite-noreply＠google.com 04 Dec '14

04 Dec '14

Status: New Owner: ---- New issue 447 by t...@timsears.com: installation breaks copy/paste feature of vmware-tools http://code.google.com/p/xmonad/issues/detail?id=447 Any idea why installing xmonad would break the copy/paste function of vmware? What steps will reproduce the problem? 1. Running Ubuntu 10.10 under VMware Fusion under macosx 10.6 (Snow Leopard) 2. apt-get install xmonad 3. Try and copy/paste from the mac into a terminal window on Ubuntu. Doesn't matter if xmonad is running or if the session has been restarted. What is the expected output? What do you see instead? Ubuntu loses track of the copy/paste buffer. What version of the product are you using? On what operating system? see above. Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". no Please provide any additional information below. The system is repaired by running "apt-get uninstall xmonad" This only uninstalls the xmonad package not it dependencies.

1 10

Re: [xmonad] Issue 177 in xmonad: xmonad does not follow ICCCM and ignores WM_TAKE_FOCUS protocol
by codesite-noreply＠google.com 03 Dec '14

03 Dec '14

Comment #127 on issue 177 by vogt.a...@gmail.com: xmonad does not follow ICCCM and ignores WM_TAKE_FOCUS protocol http://code.google.com/p/xmonad/issues/detail?id=177 losinski.j, If I were to `cabal upload' now, it's possible that you might still need to add to the logHook `setWMName "LG3D"' to get your java app to work.

1 3

Issue 350 in xmonad: Investigate using Dyre for xmonad configuration
by codesite-noreply＠google.com 03 Dec '14

03 Dec '14

Status: Accepted Owner: gwern0 Labels: Milestone-Release1.0 New issue 350 by SpencerJanssen: Investigate using Dyre for xmonad configuration http://code.google.com/p/xmonad/issues/detail?id=350 http://hackage.haskell.org/package/dyre Things we need to know before switching: * Can we make the transition seamless for our users? This means the config file format, location remain unchanged. * Is the maintainer available and cooperative? Will bug reports and patches be attended to in a timely manner? -- 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

3 16

Issue 414 in xmonad: Wrong floating window sizes on multimon setup
by codesite-noreply＠google.com 25 Nov '14

25 Nov '14

Status: New Owner: ---- New issue 414 by einars: Wrong floating window sizes on multimon setup http://code.google.com/p/xmonad/issues/detail?id=414 I have a dual monitor setup using twinview, left is 1280x1024, right - 1920x1200. The windows that should be floating in some exact sizes appear correctly on 4:3 screen, but have a bad size on the right, 16:10 monitor, having weird borders around. To reproduce, I can open, e.g winecfg on the one or other monitor; see the attached image for its appearance. Running the latest darcs version of xmonad and xmonad-contrib, can reproduce with minimal xmonad.hs, the problem doesn't appear when running single monitor. Attachments: 1920x1200.png 12.1 KB

1 6

darcs patch: needs update for mplayer2
by Joachim Breitner 20 Nov '14

20 Nov '14

1 patch for repository http://code.haskell.org/xmonad: Thu Jul 3 07:43:59 CEST 2014 Joey Hess <joeyh(a)debian.org> * needs update for mplayer2 xmonad floats mplayer by default. However, Debian has switched to mplayer2, and so on upgrade, it will stop floating. This can be easily fixed in the user's config file, but here is a patch that avoids bothering the user with breakage on upgrade.

5 6

Issue 484 in xmonad: Use XDG Base Directory Specification
by codesite-noreply＠google.com 29 Oct '14

29 Oct '14

Status: New Owner: ---- New issue 484 by cristikl...@gmail.com: Use XDG Base Directory Specification http://code.google.com/p/xmonad/issues/detail?id=484 Hello, Would it be possible to make xmonad respect the XDG Base Directory [1] specification? This would allow the user's home directory to be more organized and clearly separate configuration files, cache files and user data. For xmonad the following changes would be necessary: - move ~/.xmonad/xmonad.hs to $XDG_CONFIG_HOME/xmonad/xmonad.hs - move other generated files (like xmonad.hi) to $XDG_CACHE_HOME/xmonad/ Thanks in advance, Cristian KLEIN. [1] http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html

2 20

Issue 568 in xmonad: Actions.DynamicWorkspaceGroups viewWSGroup changes which workspace has focus incorrectly
by codesite-noreply＠google.com 14 Sep '14

14 Sep '14

Status: New Owner: ---- New issue 568 by nwfila...@gmail.com: Actions.DynamicWorkspaceGroups viewWSGroup changes which workspace has focus incorrectly http://code.google.com/p/xmonad/issues/detail?id=568 When running viewWSGroup, the focus is set to whichever display is last in the windowset's visible set. It would be better, IMHO, if focus were considered part of the WSGroup. Simply reversing the list of workspaces should mean that the last greedyView serves to restore focus to the workspace (and screen) focused-at-group-creation-time. --- old-XMonadContrib/XMonad/Actions/DynamicWorkspaceGroups.hs 2014-05-06 20:26:25.919864085 -0400 +++ new-XMonadContrib/XMonad/Actions/DynamicWorkspaceGroups.hs 2014-05-06 20:26:26.163865644 -0400 @@ -93,7 +93,7 @@ -- | Give a name to the current workspace group. addCurrentWSGroup :: WSGroupId -> X () addCurrentWSGroup name = withWindowSet $ \w -> - addWSGroup name $ map (W.tag . W.workspace) (W.current w : W.visible w) + addWSGroup name $ map (W.tag . W.workspace) (reverse $ W.current w : W.visible w) -- | Delete the named workspace group from the list of workspace -- groups. Note that this has no effect on the workspaces involved; A different, equally-defensible behavior, would be to consider the focus to not be part of the WSGroup and to hold the current focus across the viewWSGroup operation. A wrapper like this may be useful: holdScreenFocus a = do s <- gets (S.screen . S.current . windowset) r <- a screenWorkspace s >>= maybe (return ()) (windows . S.view) return r Thanks! --nwf; -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 2

Leak... somewhere... I periodically restart xmonad to recover gobs of swap space
by Michael Witten 03 Sep '14

03 Sep '14

Software: xmonad 0.11 xmobar 0.10 Xorg 1.14.1 After a while (say, a month) of normal activity, my swap space becomes almost entirely eaten up; the problem can be solved by restarting xmonad (`mod-q'). The problem could well be `xmobar' or `X' itself.

5 10

Re: Issue 168 in xmonad: gnome-panel with autohide enabled appears behind main windows
by codesite-noreply＠google.com 08 Aug '14

08 Aug '14

Comment #5 on issue 168 by govnototalitarizm: gnome-panel with autohide enabled appears behind main windows http://code.google.com/p/xmonad/issues/detail?id=168 gwern0 do not work with latest xmonad. This issue is a major stopover for me to migrate to xmonad.

1 5