- xmonad - Haskell.org

Trouble with multiple screens and Nvidia drivers
by Bárður Árantsson 15 Dec '07

15 Dec '07

Hi all, (This is all with xmonad-0.5) I've been wanting to try out xmonad (as a replacement for ion3), but I'm having some trouble with the multi-screen support, but maybe I'm just confused about how it's supposed to work... My setup is as follows: |----------------| |--------------| | Screen 1 | | Screen 0 | |----------------| |--------------| This is what the nvidia control panel says. The nvidia control panel also says that Xinerama is enabled (and so does my xorg.conf). Xdpyinfo says: default screen number: 0 number of screens: 1 and lists a screen size of 3200x1200 (my screens are both 1600x1200). As far as I understand Xinerama this is all as it should be. Moving stuff across the boundary between the two screens works as it should. Now, the behavior that seems very disconcerting to me is this: Let's say I use the Full layout exclusively and place a client (A) on workspace 1, thus: Workspace 1: Screen 1 Screen 0 |--------------| |--------------| | (empty) | | client A | |--------------| |--------------| Then I switch to workspace 4, place a client (B) which also ends up on the physical screen 0: Workspace 4: Screen 1 Screen 0 |--------------| |--------------| | (empty) | | client (B) | |--------------| |--------------| If I now switch to workspace 1 via Alt-1 and then go up through the workspaces via Alt-2, Alt-3 and Alt-4 I get the following sequence of physical layouts: Alt-2 => Workspace 2: Screen 1 Screen 0 |--------------| |--------------| | (empty) | | (empty) | |--------------| |--------------| => As it should be. Alt-3 => Workspace 3: Screen 1 Screen 0 |--------------| |--------------| | Client A | | (empty) | |--------------| |--------------| => What is client A now suddenly doing on workspace 3? Alt-4 => Workspace 4: Screen 1 Screen 0 |--------------| |--------------| | (empty) | | client (B) | |--------------| |--------------| => As it should be. Things get really weird when I go back down through the workspaces: Alt-3 => Workspace 3: Screen 1 Screen 0 |--------------| |--------------| | Client B | | (empty) | |--------------| |--------------| => What is client B now doing on the left hand side of workspace 3? Alt-2 => Workspace 2: Screen 1 Screen 0 |--------------| |--------------| | Client B | | (empty) | |--------------| |--------------| => What is client B now doing on the left hand side of workspace 2? Alt-1 => Workspace 1: Screen 1 Screen 0 |--------------| |--------------| | Client B | | Client A | |--------------| |--------------| I'm really baffled by this behavior. Am I missing something fundamental about how xmonad+Xinerama is supposed to work? (The exact order/screens which clients end up on doesn't seem to be completely reproducible; the above is what happens most of the time though). Any help in understanding this would be greatly appreciated. Cheers, -- Bardur Arantsson <bardurREMOVE(a)THISscientician.net> - I'm sorry I lied to you, Marge, but this gun had a hold on me. I felt this incredible surge of power, like God must feel when he's holding a gun. Homer Simpson, 'The Simpsons'

7 9

darcs patch: +XMonad.Util.Search: new module (and 1 more)
by gwern0＠gmail.com 14 Dec '07

14 Dec '07

Thu Dec 13 15:51:59 EST 2007 gwern0(a)gmail.com * +XMonad.Util.Search: new module This module is intended to provide helpful functions for easily running web searchs; just hit a bound key, enter your query, and up opens a new tab/browser/window with the search results. In theory anyway; the Wikipedia and Google ones work fine for me, but the Internet Archive's docs on how to do don't necessarily seem to be correct. If you were, like me, previously running shell commands to call Surfraw or similar shell scripts to do the same thing, you can now scrap them and replace them. There aren't too many search engines defined here; new ones would be good, and they're easy to add! Thu Dec 13 15:56:54 EST 2007 gwern0(a)gmail.com * +cabal support for XMonad.Util.Search

4 5

Irc channel growth
by Don Stewart 14 Dec '07

14 Dec '07

The #xmonad irc channel has almost reached 100 users. Yay. See the growth since the project started here, http://galois.com/~dons/images/hist.png If you've not dropped by #xmonad @ freenode for a chat, feel free. Cheers, Don

1 0

Issue 100 in xmonad: XMonad.Layout.ResizableTile fails if floating window present on same screen.
by codesite-noreply＠google.com 13 Dec '07

13 Dec '07

Issue 100: XMonad.Layout.ResizableTile fails if floating window present on same screen. http://code.google.com/p/xmonad/issues/detail?id=100 Comment #1 by byorgey: Hmm, I think I see the problem. The doLayout function in ResizableTile's LayoutClass instance applies its tiling to the results of W.integrate -- but W.integrate results in the entire contents of the stack, which includes any floating windows. I'll try to push a fix later today. -- 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

Tabbed Layout
by Dominik Bruhn 13 Dec '07

13 Dec '07

Hy, I got two questions: First the more general one: Serveal weeks ago here was a overviewpage with some modules and screenshots. Currently I can only find the haddok text, but there are no screenshots. I think the screenshots were quite usefull for beginners. Sometimes you can't realy imagine what a module/plugin does. The second one: Is there a possibility to add the tabbed-layout not to the whole workspace to maintain the tiled-layout and add the tabs to each of the small windows. More like ion (:/) does it. Does anybody understand what Im thinking about? Thanks a lot! -- Dominik Bruhn mailto: dominik(a)dbruhn.de

7 7

Issue 101 in xmonad: Generalise dzen binding
by codesite-noreply＠google.com 13 Dec '07

13 Dec '07

Issue 101: Generalise dzen binding http://code.google.com/p/xmonad/issues/detail?id=101 New issue report by dons00: The current dzen binding isn't composable nor extensible. Fix this. Issue attributes: Status: Accepted Owner: dons00 Labels: Type-Defect Priority-Medium Milestone-Release0.6 -- 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 100 in xmonad: XMonad.Layout.ResizableTile fails if floating window present on same screen.
by codesite-noreply＠google.com 12 Dec '07

12 Dec '07

Issue 100: XMonad.Layout.ResizableTile fails if floating window present on same screen. http://code.google.com/p/xmonad/issues/detail?id=100 New issue report by thomas.adam22: What steps will reproduce the problem? 1. Import XMonad.Layout.ResizableTile 2. Bind the MirrorExpand / MirrorShrink commands to keys as in: , ((modm, xK_a), sendMessage MirrorExpand) , ((modm, xK_z), sendMessage MirrorShrink) 3. Now place a floating window on the same screen as some tiled windows; this is irrlevant of of Xinerama, although that's what I am using. What is the expected output? What do you see instead? When focusing a window already tiled with a floating window present on the screen, the keys bounf in (2) above should shrink/expand that window, but it does not. Instead nothing happens, or something ""weird"" happens, where ""weird"" could be nothing at all, or the focused tiled window is only resizable in one direction, If I move the floating window to another monitor (assuming Xinerama), or close it, the the Mirror{Expand,Shrink} commands work as expected, Clearly something odd is happening with the presence of a floating window present, although no visible events are sent to the floating window when trying to shrink/expand a tiled window which overlaps the floating window. What version of the product are you using? On what operating system? XMonad darcs (post 0.5 release). Running on Debian Linux SID, compiled myself. Please provide any additional information below. N/A 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

darcs patch: Man.hs: input speedup
by Valery V. Vorotyntsev 12 Dec '07

12 Dec '07

Wed Dec 12 11:02:56 EET 2007 "Valery V. Vorotyntsev" <valery.vv(a)gmail.com> * Man.hs: input speedup Descend manpage directories once -- when `manPrompt' is called. (Previous version used to search directories upon each character arrival.) -- vvv

2 1

darcs patch: Run.hs: fix documentation, cleanup whitespace
by Valery V. Vorotyntsev 12 Dec '07

12 Dec '07

Wed Dec 12 11:15:16 EET 2007 "Valery V. Vorotyntsev" <valery.vv(a)gmail.com> * Run.hs: fix documentation, cleanup whitespace -- vvv

2 1

xemacs and xmonad
by Bas van Dijk 12 Dec '07

12 Dec '07

Hello, First of all, thanks for the wonderfull 0.5 release! The automatic building of '~/.xmonad/xmonad.hs' is a very time saving feature! Al dough modmask-q doesn't work for me but I will save that for another thread. Now my problem. I'm recently doing some Epigram programming and you need xemacs for that. The problem is that when xmonad is setting the size of the xemacs window, the xemacs process goes to 100% CPU usage and the xemacs window begins to flicker a lot and is just unusable. What probably happens is that when xmonad is setting the window size, xemacs wants to set it back, then xmonad sets it back, then xemacs set it back, then xmonad... ad infinitum. A workaround that I'm currently using is to use the HintedTile layout instead of the Tall layout. This works wonderfully however when using other layouts, like Circle, the problem returns. Is there a way to tell xmonad that it should respect the hints from xemacs in _every_ layout? I think I can possibly use the 'manageHook' for this. The problem with this is that emacs and xemacs have the same className. Any pointers are appreciated. regards, Bas

2 2