January 2011 - xmonad

Issue 428 in xmonad: smart borders causes flickering on worspace switch.
by codesite-noreply＠google.com 23 Jan '11

23 Jan '11

Status: New Owner: ---- New issue 428 by moreil...(a)gmail.com: smart borders causes flickering on worspace switch. http://code.google.com/p/xmonad/issues/detail?id=428 steps to reproduce 1. add smart border to your layout hook 2. spawn 2 different windows on 2 different desktops 3. optionally - set a flaring background for your root window 4. switch between desktops it's only desktop switching is affected, switching from window to window on the same desktop goes as usual. xmonad version: 0.9.1 contrib version: 0.9.1

1 0

Initial Layout
by Allan Wind 21 Jan '11

21 Jan '11

I am starting xterm, iceweasel (aka firefox) and pidgin from .xsession: iceweasel & pidgin & uxterm -e 'tmux new mutt' & exec /usr/bin/x-window-manager And using the following xmonad configuration: myManageHook = composeAll [ className =? "Gimp" --> doFloat, className =? "Iceweasel" --> doF (W.shift "1"), (className =? "Iceweasel" <&&> resource =? "Dialog") --> doFloat, className =? "Pidgin" <&&> title =? "Buddy List" --> doShift "2" ] main = xmonad $ ewmh defaultConfig { borderWidth = 1, manageHook = myManageHook <+> manageHook defaultConfig, modMask = mod4Mask, terminal = "/usr/bin/x-terminal-emulator -e tmux" } This gives me the following behavior: xterm on workspace 1 right iceweasel on workspace 1 left pidgin on workspace 2 active desktop is 2. Two questions (a) Is there a way to swap xterm and iceweasel for the initial session? (b) And how do I tell xmoand that workspace 1 should be active? I am happy to dig more into the docs. /Allan -- Allan Wind Life Integrity, LLC <http://lifeintegrity.com>

5 5

XMonad.Layout.LayoutScreens in an upside-down T arrangement
by Alistair Gee 20 Jan '11

20 Jan '11

I have 4 monitors, but I am limited two 2 X screens due to my 2 nvidia cards. My current screen setup is: +------------+------------+ | X screen 0 | X screen 1 | | monitor 1 | monitor 3 | +------------+------------+ | X screen 0 | X screen 1 | | monitor 2 | monitor 4 | +------------+------------+ That is, the nvidia driver combines monitor 1 and monitor 2 into the 1st X screen and monitor 3 and monitor 4 into a 2nd X screen. To recreate the effect of 4 separate X screens, I use XMonad.Layout.LayoutScreens to create a 2x2 screen setup. The command I have in xmonad.hs is layoutScreens 4 Grid This works well. However, I would like to rearrange my screen setup to be instead as follows: +------------+ | | | | +------------+------------+------------+ | | | | | | | | +------------+------------+------------+ Using the nvidia configuration tool, I can create the above as: +------------+ | X screen 0 | | | +------------+------------+------------+ | X screen 1 | X screen 0 | X screen 1 | | | | | +------------+------------+------------+ or +------------+ | X screen 0 | | | +------------+------------+------------+ | X screen 1 | X screen 1 | X screen 0 | | | | | +------------+------------+------------+ However, once I do that, how do I use XMonad.Layout.LayoutScreens to create a 4 screen setup again, now that the positions of the monitors are different (and I can't use Grid to split up the layout)? TIA

2 1

layoutHook, manageHook: how to use with others
by Igor 'Lo' (И.L.) 20 Jan '11

20 Jan '11

Hi all, I have: myLayout = spiral (6/7) ||| tiled ||| Mirror tiled main = xmonad defaultConfig { .. -- hooks, layouts layoutHook = showWName myLayout, manageHook = composeOne [ isFullscreen -?> doFullFloat ], .. } Is it correct to add docks support as: main = xmonad defaultConfig { .. -- hooks, layouts layoutHook = avoidStruts $ showWName myLayout, manageHook = composeOne [ isFullscreen -?> doFullFloat ] <+> manageDocks, .. } How to unite multiple layout/manage hooks? What is correct Haskell syntax? cheers, Igor

2 1

trying to get started w/ xmonad
by Sean Allen 20 Jan '11

20 Jan '11

I'm attempting to ease into using xmonad by using the gnome integration. I have a dual monitor setup and I want to turn greedy views off and have each screen have its own set of workspaces, so if I'm on the main monitor, it has its own workspace 1-9 and the same for the second screen. starting from various faqs, I came up with this: import XMonad import XMonad.Config.Gnome import XMonad.Layout.NoBorders import qualified XMonad.StackSet as W import XMonad.Util.EZConfig (additionalKeys) import XMonad.Layout.IndependentScreens main = do xmonad $ gnomeConfig { workspaces = withScreens 2 ["1", "2", "3", "4", "5", "6", "7", "8", "9"] , modMask = mod4Mask , terminal = "gnome-terminal" , layoutHook = smartBorders (layoutHook gnomeConfig) } `additionalKeys` myKeys myKeys = [ -- rebind meta-p to dmenu ((mod4Mask, xK_p), spawn "exe=`dmenu_path | dmenu` && eval \"exec $exe\"") ] ++ [ ((m .|. mod4Mask, k), windows $ onCurrentScreen f i) | (i, k) <- zip (workspaces' conf) [xK_1 .. xK_9] , (f, m) <- [(W.view, 0), (W.shift, shiftMask)] ] but conf on this line isn't in scope: | (i, k) <- zip (workspaces' conf) [xK_1 .. xK_9] gnomeConfig is in scope but that doesn't seem to make a difference and it kills the rebind for dmenu. pointers greatly appreciated.

3 3

Alt-tab behavior
by Michael Orlitzky 19 Jan '11

19 Jan '11

Is there a way to restore "typical" alt-tab behavior (i.e. what most WMs do by default)? With alt held down, each tab press will cycle forward. Release alt, press it again, and each tab now cycles backwards through the list of windows. What I *really* want from this is just a side effect: alt-tab-(release) always switches to the "last" window -- the one that was focused before the current one. I apparently have this operation burned into my brain, and I attempt to use it continually throughout the day whether it works or not.

2 2

Issue 426 in xmonad: XFT show characters outside my set font as blocks.
by codesite-noreply＠google.com 18 Jan '11

18 Jan '11

Status: New Owner: ---- New issue 426 by Dank...(a)gmail.com: XFT show characters outside my set font as blocks. http://code.google.com/p/xmonad/issues/detail?id=426 * What steps will reproduce the problem? 1. Set my font to something like Dejavu Sans/serif/mono, Liberation Sans/serif/mono, Droid Sans/Serif/Mono, etc 2. Open some xmonad tabs that should render some foreign characters like japanese or korean * What is the expected output? What do you see instead? - I see what is in the attached image. I get square blocks rather than the foreign text. in this case "日本語" is what i should see. - The problem occurs in xmobar and xmonad tabs, which i assume is a related issue. * What version of the product are you using? On what operating system? - happens on xmonad 9.1 and pulling from latest darcs - I've tested on slackware, ubuntu, arch, debian * Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". ** xmonad.hs: http://hpaste.org/43098/xmonadhs ** xmonad --recompile (no output): [dankles@mercury ~]$ xmonad --recompile [dankles@mercury ~]$ ** Other relevant info: *** ~/.fonts.conf: http://hpaste.org/paste/43098/fontsconf#p43099 * Please provide any additional information below. If I set my font to a japanese font, japanese characters will display correctly. Or if i set it to a korean font, korean fonts display fine as well. etc. This seems to be an issue of xft not falling back to another font that has the correct characters. other non-haskell xft apps seem to handle this fine. e.g. emacs, urxvt, etc.. ** X11-xft: This is actually likely to be a bug in the haskell x11-xft lib. I'm running the latest version (0.3) http://hackage.haskell.org/package/X11-xft-0.3 There is a Hello.hs test file in the X11-xft package. If compiled, I get the same exact error with foreign characters. This package hasn't been updated in nearly 3 years. I've emailed the developer, but he hasn't responded. So i'm coming to you guys, hoping that you can help me out in some way. ** Personal plug: I've been using xmonad for about a year and a half now. I had been searching for "my" WM/DE of choice for years. Ever since KDE moved to KDE4. I've tried awesome, ion, fluxbox, xfce, gnome, openbox, lxde, stumpwm, and many more... Xmonad has finally been "it" for me. And this is the only bug that has been bothering me this whole time (which is better than i can say for any other WM/DE i've tried). So I'm willing to help in ANY way on my end that i can. Thanks Attachments: 2011-01-17--1295252661_1680x1050_screen.png 335 KB

1 2

darcs patch: make prompt window width configurable
by jochen.keil＠gmail.com 18 Jan '11

18 Jan '11

1 patch for repository http://code.haskell.org/XMonadContrib: Fri Jan 14 22:41:21 CET 2011 jochen.keil(a)gmail.com * make prompt window width configurable This allows the prompt window to be placed at the center of the screen with a custom width (defaults to spanning the whole screen)

2 1

Re: [xmonad] Issue 307 in xmonad: pidgin message windows change repeatedly grow on a multi-monitor setup
by codesite-noreply＠google.com 16 Jan '11

16 Jan '11

Comment #2 on issue 307 by marcin.r...(a)gmail.com: pidgin message windows change repeatedly grow on a multi-monitor setup http://code.google.com/p/xmonad/issues/detail?id=307 I can confirm: I have 2 monitor setup (bigger/smaller) and I have the same issue with Psi and Pidgin (both have 'remember window sizes' setting enabled). Each time the window is opened it gets bigger. Any ideas?

1 4

PATCH HCAR, was, Re: Your HCAR November 2010 material
by Gwern Branwen 16 Jan '11

16 Jan '11

On Tue, Nov 9, 2010 at 3:27 PM, Janis Voigtlaender <hcar(a)haskell.org> wrote: > Dear Gwern, > > The November 2010 edition of the Haskell Communities and > Activities Report (HCAR) has been published: > > http://www.haskell.org/pipermail/haskell/2010-November/022366.html > > This edition of HCAR contains material from you on the > following topics: > > * mueval > * xmonad > > The articles in the form contained in the report are attached to > this mail. Please replace your local copies with these .tex files > (possibly adapted by me) *now*. > > Doing so helps avoid repeated work when the next edition is due > in six months, hopefully with further contribution from you. > > And THANK YOU for your contribution to the current report! > > Best, > Janis. Attached is a patch bundle with my previous HCAR.tex patches and also a new patch which simply records the diff of Janis's changes made to the HCAR.tex. I'm not a Latex expert so I'm not entirely sure what they're all about, but they look like small syntax fixes, so nothing controversial. -- gwern http://www.gwern.net

2 1