March 2011 - xmonad - Haskell.org

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 396 in xmonad: Qt (and KDE) don't display menu if not on first display
by codesite-noreply＠google.com 24 Nov '11

24 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

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

18 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 11 Nov '11

11 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

Issue 372 in xmonad: Changes made to defaultConfig do not take on recompile and restart.
by codesite-noreply＠google.com 04 Sep '11

04 Sep '11

Status: New Owner: ---- New issue 372 by aditya.siram: Changes made to defaultConfig do not take on recompile and restart. http://code.google.com/p/xmonad/issues/detail?id=372 What steps will reproduce the problem? 1. change any defaultConfig setting, in my case change terminal = "gnome-termimal" to terminal = "xterm", recompile (xmonad --recompile) and restart(xmonad --restart) What is the expected output? What do you see instead? mod-shift-return should now pull up an xterm. Instead it still opens a gnome-terminal. What version of the product are you using? On what operating system? 0.9.1, Ubuntu Karmic Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". config file is attached. Recompile step has no output. Attachments: xmonad.hs 2.0 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 1

Issue 328 in xmonad: RunOrRaise and dbus(?)
by codesite-noreply＠google.com 04 Sep '11

04 Sep '11

Status: New Owner: ---- New issue 328 by grapescan: RunOrRaise and dbus(?) http://code.google.com/p/xmonad/issues/detail?id=328 What steps will reproduce the problem? 1. Set some bindings like this: ("M-t", runOrRaise "transmission" (className =? "Transmission")) or ("M-w", runOrRaise "firefox" (className =? "Shiretoko")) 2. Try to run these programs with created shortcuts 3. Try to run these programs without created shortcuts (i.e. from terminal or gmrun) What is the expected output? What do you see instead? Starting from terminal or gmrun looks fine while using shortcuts causes strange behavior. Firefox complains about connecting to session: "/usr/bin/dbus-launch terminated abnormally without any error message". Transmission doesn't want to open torrents from Firefox (torrents opened with Transmission from web-browser). It says something like "Transmission is already started." What version of the product are you using? On what operating system? I use actual version of ArchLinux. I checked dbus packages - they seem to be OK. Packages xmonad-darcs and xmonad-contrib-darcs built a few weeks ago. Attachments: xmonad.hs 5.3 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 3

Re: Issue 322 in xmonad: Background shown when workspace switches
by codesite-noreply＠google.com 17 Aug '11

17 Aug '11

Comment #2 on issue 322 by sgsoftware: Background shown when workspace switches http://code.google.com/p/xmonad/issues/detail?id=322 I am not sure that this is strictly an X server problem since I've got similar behavior after upgrading xmonad from version 0.8.1 to version 0.9. Apparently something has changed in between and now xmonad draws background so that it is very noticeable (and quite annoying). In the previous version of xmonad switching between two full-screen windows was immediate and I could see no background. -- 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 6

Issue 325 in xmonad: Layout.Spacing breaks Layout.WindowNavigation
by codesite-noreply＠google.com 15 Aug '11

15 Aug '11

Status: New Owner: ---- New issue 325 by OrbisVicis: Layout.Spacing breaks Layout.WindowNavigation http://code.google.com/p/xmonad/issues/detail?id=325 Removing the spacing modifier in the layoutHook or setting "spacing 0" fixes the problem. Symptoms: While Go or Swap *might* initially work, they very quickly lock up and do nothing. -- 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 9

Issue 373 in xmonad: Hlintify XMonad & XMonadContrib
by codesite-noreply＠google.com 10 Aug '11

10 Aug '11

Status: Accepted Owner: gwern0 Labels: Type-Enhancement Priority-Low Component-Contrib Maintainability Component-Core New issue 373 by gwern0: Hlintify XMonad & XMonadContrib http://code.google.com/p/xmonad/issues/detail?id=373 Hlint (http://community.haskell.org/~ndm/hlint/) is a code-style tool that flags verbose, useless, or otherwise bad bits of code. It would be good if XMC had clean code. (Hlint strives for 'correctness'; none of the changes ought to affect the semantics of the code.) XMonad-core generates roughly 31 suggestions and XMC roughly 468. Even excluding debatable suggestions like eta-reduction, this is a lot of small bad things. Fortunately, they are all generally very easy to fix and understand why the code was flagged, making this a good beginner project. Attached are the 2 HTML reports hlint generates (obviously 31+468 messages is a bit much to paste in). Attachments: core.html 38.5 KB xmc.html 528 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 2

Issue 359 in xmonad: shellPromptHere from XMonad.Actions.SpawnOn doesn't work as claimed
by codesite-noreply＠google.com 05 Aug '11

05 Aug '11

Status: New Owner: ---- New issue 359 by wei.hoo: shellPromptHere from XMonad.Actions.SpawnOn doesn't work as claimed http://code.google.com/p/xmonad/issues/detail?id=359 What steps will reproduce the problem? 1. Bind a key combination to shellPromptHere 2. On workspace 1, spawn a slow-starting program, say opera, using shellPromptHere 3. Switch to workspace 2 What is the expected output? The program is placed on workspace 1 where I started the program. What do you see instead? The program shows up on the current workspace, #2. What version of the product are you using? On what operating system? xmonad-darcs and xmonad-contrib-darcs on Arch Linux. Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". Please provide any additional information below. As a general question, how do I go about debugging issues like this? In particular, how do I write out debugging information to files/console/screen? Attachments: xmonad.hs 6.8 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 9