August 2009 - xmonad - Haskell.org

Re: [xmonad] Problem with Multi-head setup
by wagnerdm＠seas.upenn.edu 24 Aug '09

24 Aug '09

Here is the way I understand it. Likely some of the following statements will be subtly wrong, and I apologize in advance for spreading my misconceptions about X. There are two distinct pieces of X called Xinerama. One of the pieces is a set of library calls used for communicating the size and locations of physical screens in logical space within a single DISPLAY. xmonad uses these library calls to break your physical screens into separate logical workspaces. As such, the library called xinerama is required for multi-head support. However, I understand that there are other ways of controlling multiple monitors, in particular running several different DISPLAYs under X, one for each screen. You may of course do this; then you must start a separate xmonad instance for each DISPLAY. There is currently no integration for this; i.e. no way to send windows from one DISPLAY to another (though I hear rumors that some window managers do have such capabilities). Other than those two options, I am not familiar with any other way of driving multiple monitors. Cheers, ~d Quoting Eric Thomas <eric.l.m.thomas(a)gmail.com>: > Sorry for the noob question, but why is xinerama required for xmonad to > work? > As I understand it, xinerama just makes your multi head setup appear as > though there is one long screen. > However, I like it when my screens are treated as two different desktops. > Does xmonad not support this? > > Eric Thomas > > > > On Sat, Aug 22, 2009 at 4:55 PM, <wagnerdm(a)seas.upenn.edu> wrote: > >> Hi Eric, >> >> It sounds like you haven't got the Xinerama extension running; getting that >> set up is not xmonad-specific. There are many excellent tutorials on >> setting up Xinerama on the web; Google should help here. (For example, try >> "setting up Xinerama", which pointed me to < >> http://www.ibiblio.org/pub/Linux/docs/HOWTO/Xinerama-HOWTO>.) It also >> depends slightly on what graphics card you are using. If you've got an >> nvidia card with the proprietary nvidia drivers, check out the man pages for >> nvidia-xconfig; other people here may have other suggestions for other >> cards. >> >> Cheers, >> ~d >> >> >> Quoting Eric Thomas <eric.l.m.thomas(a)gmail.com>: >> >> Hello, >>> >>> When attempting to setup xmonad on a dual setup, I cannot use the keyboard >>> on the second monitor. >>> >>> The following command: >>> ghc -e "Graphics.X11.openDisplay [] >>= >>> Graphics.X11.Xinerama.getScreenInfo" >>> >>> generates this output: >>> Xlib: extension "XINERAMA" missing on display ":0.1". >>> [Rectangle {rect_x = 0, rect_y = 0, rect_width = 1280, rect_height = >>> 1024}] >>> >>> In the FAQ, its says to check my Xserver configuration, but I don't know >>> what I need to check. >>> >>> Any help would be appreciated. >>> >>> Thanks, >>> >>> Eric >>> >>> >> >> >

3 4

moving windows with mouse and named workspaces
by Ramon Diaz-Uriarte 24 Aug '09

24 Aug '09

Dear All, I am new to Xmonad, coming to it from other tiling wm (wmii for the last year or so, ion before that). I am very much enjoying it (the feel, the intuitiveness, the great docs, the large number of extra available stuff, etc), but I have two questions: 1. Is it possible to move (and resize) windows with the mouse? This is immediate in wmii (and also doable in awesome). I have found some info in the mailing list, but I am not still fully clear about how to do it. http://article.gmane.org/gmane.comp.lang.haskell.xmonad/4491/match=mouse+re… 2. A feature I miss a lot from wmii is the creation of workspaces "on the fly", with whatever name I care to use. Then, I can move to that workspace by name. When I am done there (i.e., it gets emptied) it disappears automagically. (To be more clear, this is an example of usage: say Mary comes for help on some analysis; I create a new workspace called "Mary", and there I fire up xterm, emacs, whatever. That remains open maybe for days, until done. In the meantime, Fred might come along with another different request; I creat a workspace for Fred. And, of course, I've kept open for the last months the workspace named "web", etc, etc. It is easer for me to move around by "name" than remembering where I left the emacs session with Mary's analysis). If searched and found a few hits, but again I do not see how to actually do it: http://article.gmane.org/gmane.comp.lang.haskell.xmonad/2727/match=name+wor… http://article.gmane.org/gmane.comp.lang.haskell.xmonad/883/match=name+work… Thanks for such a nice piece of work. Best, R. -- Ramon Diaz-Uriarte Structural Biology and Biocomputing Programme Spanish National Cancer Centre (CNIO) http://ligarto.org/rdiaz Phone: +34-91-732-8000 ext. 3019

2 3

Issue 311 in xmonad: using noBorders on tabbed layout freezes tab bar on workspace change
by codesite-noreply＠google.com 24 Aug '09

24 Aug '09

Comment #1 on issue 311 by pbrisbin: using noBorders on tabbed layout freezes tab bar on workspace change http://code.google.com/p/xmonad/issues/detail?id=311 should've been (tabbed shrinkText myTabConfig) sorry, the attached xmonad.hs is accurate. -- 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 311 in xmonad: using noBorders on tabbed layout freezes tab bar on workspace change
by codesite-noreply＠google.com 24 Aug '09

24 Aug '09

Status: New Owner: ---- New issue 311 by pbrisbin: using noBorders on tabbed layout freezes tab bar on workspace change http://code.google.com/p/xmonad/issues/detail?id=311 What steps will reproduce the problem? 1. add something like this to your layouts myLayouts = tabLayout ||| ... where tabLayout = noBorders (tabbed shrinkWindow myTabConfig) -- fill in a custom config myTabConfig = defaultConfig { ... } 2. M-q and M-S-space, choose the tabbed layout and open some windows 3. navigate to another workspace, navigate back 4. observe that the tab bar is now frozen and does not update 5. M-S-space fixes this, but the problem occurs on every workspace change can noBorders be used this way? What version of the product are you using? On what operating system? darcs revision 20090823-1 of xmonad and xmonad-contrib on arch linux 64 bit Please provide any additional information below. i apologize in advance if it's my own lack of haskell knowledge causing this issue; my full xmonad.hs is attached. Attachments: xmonad.hs 10.2 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 0

Issue 309 in xmonad: xmonad fails with ghc 6.10.4
by codesite-noreply＠google.com 23 Aug '09

23 Aug '09

Comment #5 on issue 309 by daniel.wagner: xmonad fails with ghc 6.10.4 http://code.google.com/p/xmonad/issues/detail?id=309 It may be enough to just run the register.sh scripts in /usr/share/haskell. -- 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 310 in xmonad: XMonad.Main.handle eats WM_NAME property changes
by codesite-noreply＠google.com 23 Aug '09

23 Aug '09

Status: New Owner: ---- New issue 310 by amdragon: XMonad.Main.handle eats WM_NAME property changes http://code.google.com/p/xmonad/issues/detail?id=310 Because XMonad.Main.handle intercepts PropertyEvent X events with atom WM_NAME in order to trigger the logHook, these PropertyEvent events are never broadcast to the layout message handler. Simply adding a call to broadcastMessage is this clause of the handle function would fix this. What steps will reproduce the problem? 1. With decorations in the layout hook, run the attached program. 2. Click on the window created by the program. What is the expected output? What do you see instead? The window sets its WM_NAME property when clicked. I would expect the title in its decoration to change, but it doesn't until some other property changes (for example, by changing focus to another window). If there is a log hook that reports window titles (for example, to dzen), then the title there changes immediately. This happens because the decoration layout modifier never receives the WM_NAME property change and thus doesn't notice the title change until it receives some other property change. This is a somewhat contrived example for the sake of reproducibility, but I have similar problems fairly frequently with xterm and, I believe, emacs titles. What version of the product are you using? On what operating system? xmonad 0.8.1 on Debian unstable. The code in darcs appears to do the same thing, though I did not try running it. Attachments: wmname.c 846 bytes -- 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 309 in xmonad: xmonad fails with ghc 6.10.4
by codesite-noreply＠google.com 23 Aug '09

23 Aug '09

Comment #4 on issue 309 by mattc...(a)earthlink.net: xmonad fails with ghc 6.10.4 http://code.google.com/p/xmonad/issues/detail?id=309 OK so I need to recompile or reinstall my ghc libraries. Exactly how is this done? When you say libraries are you referring to libraries specific to ghc or specific to xmonad? Unfortunately I don't see any ghc update packages for arch linux. It seems strange that you would have a package that updates ghc without updating the libraries. When I used ghc on windows I did this simply by updating some environment variables with the correct paths, when I started a cmd shell. In this way I could switch between versions. Is this then an arch linux issue? -- 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

Problem with Multi-head setup
by Eric Thomas 22 Aug '09

22 Aug '09

Hello, When attempting to setup xmonad on a dual setup, I cannot use the keyboard on the second monitor. The following command: ghc -e "Graphics.X11.openDisplay [] >>= Graphics.X11.Xinerama.getScreenInfo" generates this output: Xlib: extension "XINERAMA" missing on display ":0.1". [Rectangle {rect_x = 0, rect_y = 0, rect_width = 1280, rect_height = 1024}] In the FAQ, its says to check my Xserver configuration, but I don't know what I need to check. Any help would be appreciated. Thanks, Eric

1 0

darcs patch: More flexible interface for X.H.FadeInactive
by Daniel Schoepe 21 Aug '09

21 Aug '09

Fri Aug 21 22:39:36 CEST 2009 Daniel Schoepe <daniel.schoepe(a)gmail.com> * More flexible interface for X.H.FadeInactive This patch allows setting the opacity on a per-window basis and lets the user specify it as a percentage instead of an Integer between 0 and 2^32-1.

1 0

Issue 309 in xmonad: xmonad fails with ghc 6.10.4
by codesite-noreply＠google.com 21 Aug '09

21 Aug '09

Comment #3 on issue 309 by daniel.schoepe: xmonad fails with ghc 6.10.4 http://code.google.com/p/xmonad/issues/detail?id=309 I don't think that would solve the general issue though, since the problem is, that xmonad and xmonad-contrib aren't registered/built for the new ghc version and removing old interface files wouldn't solve this. -- 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