February 2010 - xmonad

darcs patch: Pass extensible state via an environment variable when restarting
by Daniel Schoepe 06 Apr '10

06 Apr '10

Sat Nov 14 01:10:19 CET 2009 Daniel Schoepe <daniel.schoepe(a)gmail.com> * Pass extensible state via an environment variable when restarting This fixes a crash when an old xmonad binary would receive an additional state argument.

2 3

Several new modules (patch flood)
by Quentin Moser 01 Apr '10

01 Apr '10

Hello XMonad, I apologize for the bulk delivery, these are all things I wrote over the last week and I didn't really want to stop coding to send updates (or eat, or sleep, for that matter --). The basic idea was to implement the layout used in wmii. For those not familiar with it: - Windows grouped in resizable columns - Each column has its own sub-layout, either full, vertical or "stacked decoration" - You can of course move windows between columns, create new columns, etc. This gave rise to a number of modules, which the rest of this mail describes. To get a quick idea, you can also look at the few screenshots I put up: http://ceii.posterous.com/new-xmonad-layout. #1: XMonad.Layout.Groups A generic version of the wmii thing: windows arranged into groups, each with its own sub-layout. You provide both the (starting) layout for new groups, and the layout that arranges the groups themselves on the screen. Tis doesn't fit XMonad's layout interface that well, and indeed I ended up having to completely decouple the layout's idea of window ordering from XMonad's. For this reason, the usual swapUp/Down and focusUp/Down don't work here; the Groups module provides messages that can be used instead, and see #2 for a more flexible interface. #2: XMonad.Layout.Groups.Examples You can do a lot of fun things with the Groups combinator, so I put a few examples in a dedicated module. It also contains many useful X actions for Groups layouts, including focusUp/Down, swapUp/Down, etc. actions that work both for them and for standard layouts (using X.A.MessageFeedback). There are three example layouts: - The wmii layout, pretty faithfully cloned with the exception that I was too lazy to write a stacked layout and used tabs instead. The columns are managed by a ZoomRow (#3), so they can be individually resized and/or maximized. - A "row of columns" layout, with both rows and columns using ZoomRows. - A "tiled tabs" layout that arranges windows into tabbed groups, and the groups themselves according to XMonad's default algorithm (Tall ||| Mirror Tall ||| Full) #3: XMonad.Layout.ZoomRow A layout that arranges its windows into a horizontal row, and allows to freely resize each of them using ZoomMessages. #4: XMonad.Layout.Renamed A LayoutModifier and DSL for modifying the description of a layout. This is for when you want to modify a layout with a dynamic description, and using Named would freeze it. #5: XMonad.Util.Stack I ended up doing quite a bit of non-trivial (Maybe Stack) manipulation, so I wrote a separate module for that. It provides maps, folds, filters and the like, as well as the whole focusUp/Down-swapUp/Down-insertUp/Down suite with consistent types. I've been using these for a few pretty active days now but they are by no means fully tested, feedback is welcome.

6 7

Compile-time verification of keymaps
by Gwern Branwen 28 Mar '10

28 Mar '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 So today I edited into my xmonad.hs a binding to the Isohunt.com XMonad.Actions.Search engine for convenience. I naturally chose xK_i for the bound key. When I reloaded, I was surprised to see that mod-i failed to do as it was supposed to. Trying it again, it brought up irssi. That was when I realized mod-i had already been bound in my xmonad.hs, to runOrRaise for irssi, and that the irssi binding happened to be later in the list and so it quietly overwrote the Isohunt binding. After picking a new & unused key, I began reflecting on this. Certainly, this is expected behavior if you're familiar with Data.Map. fromList will do that - a list may have multiple values for a single key (such as xK_i) and the last value wins. But I think in an xmonad.hs, the context is somewhat different. There the semantics are somewhat different. We use 'M.fromList [stuff, more stuff, and the rest]' syntax because Haskell supports list syntax, and it makes life easier on the user to use such a common method. But do we *really* mean to say that it is a sensible thing to bind the same key to multiple contradictory definitions? It just so happens that [xK_i isohunt, xK_i irssi] is equivalent to a destructive update style of 'i = isohunt; i = irssi' when fed through the Map functions. So I thought to myself that maybe there was some static way of specifying a list without duplicates we could use in xmonad.hs. It would be nice to know that one cannot run xmonad.hs with inconsistent sets of bindings*. This checking would, even better, be done at compile-time so one could verify this by simply loading in GHCi (good for everyone who routinely reloads in Emacs or Vim). How to do this? Someone in #haskell suggested extensible records, but that sounds quite difficult. Another approach would be to scrap the static requirement, and simply provide the user a redefined 'fromList' which runs something like 'let x = map fst list in nub x == x' and does something if there are duplicates (calls error, spawns xmessage, etc.) I decided to try a variant of the latter at compile-time, using Template Haskell. I got fairly far with the help of mmorrow, but I didn't actually succeed. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREKAAYFAkkgYvgACgkQvpDo5Pfl1oLE3gCgkuHMlUO1+YT4oEFLzhHqmeuB QA4An3X72j1z+StumSOmnTXlTJhHeTft =fBDz -----END PGP SIGNATURE----- The idea is that one should be able to do something like this in xmonad.hs > '{-# LANGUAGE TemplateHaskell #-} > import XMonad.Utils.VerifyKeys > .... > myKeys conf@(XConfig {modMask = m}) = M.fromList $(uniqueTupleListQ [ -- rebind standard actions > ((m .|. shiftMask,xK_p), shellPrompt greenXPConfig) > , ((m, xK_d), raiseBrowser) ] ) VerifyKeys looks something like this: > {-# LANGUAGE TemplateHaskell #-} > module XMonad.Utils.VerifyKeys where > > import Data.List(nub) > import qualified Data.Map > import Language.Haskell.TH.Lib > import Language.Haskell.TH.Syntax > > uniqueTupleListQ :: (Eq a, Lift a, Lift b) => [(a, b)] -> ExpQ > uniqueTupleListQ xs = let ys = map fst xs > ns = nub ys > in case ys == ns of > False -> fail "uniqueTupleListQ: List has conflicting entries." > True -> lift xs The idea is that since we know the keymap at compile-time, we pass it, before it gets turned into a Map (and the relevant information lost), we analyze the list. 'fail' aborts the compilation if the list is bad. You can easily test this out in a different module with some simple expressions: > keymap1, keymap2 :: [(Char, String)] > keymap1 = $(uniqueTupleListQ [('a', "foo"), ('b', "bar")] ) > keymap2 = $(uniqueTupleListQ [('a', "foo"), ('b', "bar"), ('c', "bar"), ('a', "quux")] ) Compiling, this gives us something like this: > [1 of 2] Compiling Tmp ( Tmp.hs, Tmp.o ) > [2 of 2] Compiling Main ( xmonad.hs, xmonad.o ) > Loading package base ... linking ... done. > Loading package array-0.1.0.0 ... linking ... done. > Loading package packedstring-0.1.0.0 ... linking ... done. > Loading package containers-0.1.0.1 ... linking ... done. > Loading package pretty-1.0.0.0 ... linking ... done. > Loading package template-haskell ... linking ... done. > > xmonad.hs:113:12: uniqueTupleListQ: List has conflicting entries. Line 133 is keymap2. If we remove '('a', "quux")', which conflicts with the very first entry, we get: > [1 of 2] Compiling Tmp ( Tmp.hs, Tmp.o ) > [2 of 2] Compiling Main ( xmonad.hs, xmonad.o ) > Loading package base ... linking ... done. > Loading package array-0.1.0.0 ... linking ... done. > Loading package packedstring-0.1.0.0 ... linking ... done. > Loading package containers-0.1.0.1 ... linking ... done. > Loading package pretty-1.0.0.0 ... linking ... done. > Loading package template-haskell ... linking ... done. > Linking foo ... Now, this seems to be exactly what we want, doesn't it? But ultimately I had to admit failure. Template Haskell has a number of restrictions and omissions that make it unfeasible to use. For starters: If we apply uniqueTupleList to an actual keymap (like mine), we discover that uniqueTupleList's constraints are unworkable. Per the type sig, we need 'Lift b', the second half of each tuple in the key list. But XMonad requires b to be a X (), and X () is not instantiated for Lift**. Were it, we would still need Lift instances for Word64 and also CUInt. Lift instances probably wouldn't be too hard to write. The real killer, from an xmonad.hs perspective, is the module restrictions. Fundamentally, one *cannot* use inside a $() anything defined in the same file. {modMask = m}? Nope. greenXPConfig? Nope. 'term = XMonad.terminal conf'? Nope. And so on. It is a minimal set of bindings indeed which only makes use of literals and imported functions. So until Template Haskell improves, that avenue seems to be out. I'm not sure where to go from here. Had Template Haskell worked out, the path would've been easy, a matter of having users make a relatively small modification to their xmonad.hs, and perhaps avoiding entirely TH syntax. Does anyone have a better approach, or is this a foolish thing to want static safety in? ksf suggested that Yi has a combinator approach to keybindings which could solve it, but I am unsure how that works or could be adapted for XMonad.*** * Obviously the consistency is only valuable _in_ a specific Map; if we insisted that all Maps be consistent, then we couldn't override the default Map with our own. ** I may be misinterpreting the type error; possibly we actually need Lift for (X()) *** I'm cc'ing yi-devel since I suspect the topic may be of interest. -- gwern

5 7

darcs patch: Replace custom forever_ with library equivalent
by Daniel Schoepe 27 Mar '10

27 Mar '10

Replaced a custom forever implementation in Main.hsc by the equivalent from the standard libraries. I guess it was legacy code, since forever wasn't in Control.Monad in ghc 6.6 as far as I know. Wed Jan 14 22:55:56 CET 2009 Daniel Schoepe <asgaroth_(a)gmx.de> * Replaced custom forever_ by library function New patches: [Replaced custom forever_ by library function Daniel Schoepe <asgaroth_(a)gmx.de>**20090114215556] { hunk ./XMonad/Main.hsc 146 userCode $ startupHook initxmc -- main loop, for all you HOF/recursion fans out there. - forever_ $ prehandle =<< io (nextEvent dpy e >> getEvent e) + forever $ prehandle =<< io (nextEvent dpy e >> getEvent e) return () where hunk ./XMonad/Main.hsc 150 - forever_ a = a >> forever_ a - -- if the event gives us the position of the pointer, set mousePosition prehandle e = let mouse = do guard (ev_event_type e `elem` evs) return (fromIntegral (ev_x_root e) } Context: [Call logHook as the very last action in windows Spencer Janssen <spencerjanssen(a)gmail.com>**20081209233700 Ignore-this: 4396ad891b607780f8e4b3b6bbce87e ] [Accept inferior crossing events. This patch enables fmouse-focus-follows-screen Spencer Janssen <spencerjanssen(a)gmail.com>**20081205045130 Ignore-this: 3ac329fb92839827aed0a4370784cabd ] [Tile all windows at once Spencer Janssen <spencerjanssen(a)gmail.com>**20081118074447] [Factor rational rect scaling into a separate function Spencer Janssen <spencerjanssen(a)gmail.com>**20081118072849] [Change screen focus by clicking on the root window. Spencer Janssen <spencerjanssen(a)gmail.com>**20081106224031 This is a modification of a patch from Joachim Breitner. ] [Fix #192. Spencer Janssen <spencerjanssen(a)gmail.com>**20081021220059] [select base < 4 for building on ghc 6.10 Adam Vogt <vogt.adam(a)gmail.com>**20081013214509] [add killWindow function Joachim Breitner <mail(a)joachim-breitner.de>**20081005001804 This is required to kill anything that is not focused, without having to focus it first. ] [add'l documentation Devin Mullins <me(a)twifkak.com>**20080927234639] [Regression: ungrab buttons on *non* root windows Spencer Janssen <spencerjanssen(a)gmail.com>**20081007214351] [Partial fix for #40 Spencer Janssen <spencerjanssen(a)gmail.com>**20081007212053 Improvements: - clicking on the root will change focus to that screen - moving the mouse from a window on a screen to an empty screen changes focus to that screen The only remaining issue is that moving the mouse between two empty screens does not change focus. In order to solve this, we'd have to select motion events on the root window, which is potentially expensive. ] [Track mouse position via events received Spencer Janssen <spencerjanssen(a)gmail.com>**20081007203953] [Fix haddock Spencer Janssen <spencerjanssen(a)gmail.com>**20081007094641] [Move screen locating code into pointScreen Spencer Janssen <spencerjanssen(a)gmail.com>**20081007094207] [Make pointWithin a top-level binding Spencer Janssen <spencerjanssen(a)gmail.com>**20081007090229] [sp README, CONFIG, STYLE, TODO gwern0(a)gmail.com**20080913024457] [Use the same X11 dependency as xmonad-contrib Spencer Janssen <spencerjanssen(a)gmail.com>**20080921061508] [Export focusUp' and focusDown' -- work entirely on stacks Spencer Janssen <spencerjanssen(a)gmail.com>**20080911214803] [add W.shiftMaster, fix float/tile-reordering bug Devin Mullins <me(a)twifkak.com>**20080911053909] [TAG 0.8 Spencer Janssen <spencerjanssen(a)gmail.com>**20080905195412] [Spelling. Any bets on how long this has been there? Spencer Janssen <spencerjanssen(a)gmail.com>**20080905195211] [Bump version to 0.8 Spencer Janssen <spencerjanssen(a)gmail.com>**20080905194225] [Remove obsolete comments about darcs X11 Spencer Janssen <spencerjanssen(a)gmail.com>**20080905194915] [Recommend latest packages rather than specific versions Spencer Janssen <spencerjanssen(a)gmail.com>**20080905194837] [Also remove -optl from the executable section Spencer Janssen <spencerjanssen(a)gmail.com>**20080820210023] [-optl-Wl,-s is not needed with recent Cabal versions Spencer Janssen <spencerjanssen(a)gmail.com>**20080820204102] [Haddock links Malebria <malebria(a)riseup.net>**20080601212515] [Haddock syntax for enumeration Malebria <malebria(a)riseup.net>**20080601204951] [I prefer the spencerjanssen(a)gmail.com address now Spencer Janssen <spencerjanssen(a)gmail.com>**20080714202650] [Raise windows in the floating layer when moving or resizing Trevor Elliott <trevor(a)galois.com>**20080521215057] [add currentTag convenience function Devin Mullins <me(a)twifkak.com>**20080511224258] [Make Mirror a newtype Spencer Janssen <sjanssen(a)cse.unl.edu>**20080508104640] [Comments Spencer Janssen <sjanssen(a)cse.unl.edu>**20080507013122] [Break long line Spencer Janssen <sjanssen(a)cse.unl.edu>**20080507012608] [Style Spencer Janssen <sjanssen(a)cse.unl.edu>**20080507012519] [Simplify Spencer Janssen <sjanssen(a)cse.unl.edu>**20080507011309] [Overhaul Choose, fixes issue 183 Spencer Janssen <sjanssen(a)cse.unl.edu>**20080506220809] [Remember if focus changes were caused by mouse actions or by key commands Klaus Weidner <kweidner(a)pobox.com>**20080502175603 If the user used the mouse to change window focus (moving into or clicking on a window), this should be handled differently than focus changes due to keyboard commands. Specifically, it's inappropriate to discard window enter/leave events while the mouse is moving. This fixes the bug where a fast mouse motion across multiple windows resulted in the wrong window keeping focus. It's also helpful information for contrib modules such as UpdatePointer - it's supposed to move the mouse pointer only in response to keyboard actions, not if the user was moving the mouse. ] [Wibble Spencer Janssen <sjanssen(a)cse.unl.edu>**20080506203840] [Added doShift function for more user-friendly hooks Ivan N. Veselov <veselov(a)gmail.com>**20080506185757] [use named colours. fixes startup failure on the XO Don Stewart <dons(a)galois.com>**20080502210149] [Set focus *after* revealing windows Spencer Janssen <sjanssen(a)cse.unl.edu>**20080407222559] [Reveal windows after moving/resizing them. Spencer Janssen <sjanssen(a)cse.unl.edu>**20080407220756 This should reduce the number of repaints for newly visible windows. ] [Hide newly created but non-visible windows (fixes bug #172) Spencer Janssen <sjanssen(a)cse.unl.edu>**20080430014012] [formatting, eta expansion Don Stewart <dons(a)galois.com>**20080418184337] [XMonad.ManageHook: add 'appName', another name for 'resource' Lukas Mai <l.mai(a)web.de>**20080406012006] [XMonad.ManageHook: make 'title' locale-aware; haddock cleanup Lukas Mai <l.mai(a)web.de>**20080406011338 The code for 'title' was stolen from getname.patch (bug #44). ] [XMonad.Main: call setlocale on startup Lukas Mai <l.mai(a)web.de>**20080406011234] [floats always use current screen (with less bugs) robreim(a)bobturf.org**20080405135009] [XMonad.Operations: applySizeHint reshuffle Lukas Mai <l.mai(a)web.de>**20080404215615 Make applySizeHints take window borders into account. Move old functionality to applySizeHintsContents. Add new mkAdjust function that generates a custom autohinter for a window. ] [XMonad.Layout: documentation cleanup Lukas Mai <l.mai(a)web.de>**20080404215444] [Remove gaps from the example config Spencer Janssen <sjanssen(a)cse.unl.edu>**20080329232959] [Remove gaps Spencer Janssen <sjanssen(a)cse.unl.edu>**20080325091526] [TAG 0.7 Spencer Janssen <sjanssen(a)cse.unl.edu>**20080329210249] Patch bundle hash: ef4a14f0e22b06712aac9975c8df956a9b2846ba

7 11

darcs patch: add entries from .ssh/config to ssh prompt completion
by Brent Yorgey 25 Mar '10

25 Mar '10

See attached. Comments? -Brent

3 3

darcs patch: spawnDescendantOn
by wagnerdm＠seas.upenn.edu 22 Mar '10

22 Mar '10

Tue Sep 1 00:42:18 EDT 2009 Daniel Wagner <daniel(a)wagner-home.com> * add spawnOn-alikes that watch for child processes spawnOn is insufficient because many programs are simply shell scripts wrapping the real application. This adds some functions that watch for child processes, which treats these scripts properly. Notably, launchers like dmenu are dealt with this way.

6 7

Re: Issue 352 in xmonad: Fail to build with darcs X11 binding
by codesite-noreply＠google.com 22 Mar '10

22 Mar '10

Updates: Summary: Fail to build with darcs X11 binding Comment #2 on issue 352 by vogt.adam: Fail to build with darcs X11 binding http://code.google.com/p/xmonad/issues/detail?id=352 (No comment was entered for this change.) -- 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 8

Issue 370 in xmonad: Xinerama, CycleWS & Empt workspaces
by codesite-noreply＠google.com 24 Feb '10

24 Feb '10

Status: New Owner: ---- New issue 370 by seansorrell: Xinerama, CycleWS & Empt workspaces http://code.google.com/p/xmonad/issues/detail?id=370 What steps will reproduce the problem? 1. On a Xinerama setup, pull up one workspace with a window, and one without 2. From the workspace with the window, use a keybinding to call XMonad.Actions.CycleWS nextScreen (or prevScreen) What is the expected output? What do you see instead? The cursor _should_ jump reliably to the screen without the window, but it only works about 3 times out of 10. Suggestion: move the cursor over a few extra pixels to ensure that it really is on the correct screen What version of the product are you using? On what operating system? xmonad 0.9 on Archlinux 64-bit nVidia 9800GT Attachments: xmonad.hs 5.7 KB xorg.conf 1.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 2

Issue 375 in xmonad: keysResizeWindow doesn't always work
by codesite-noreply＠google.com 23 Feb '10

23 Feb '10

Status: New Owner: ---- New issue 375 by wei.hoo: keysResizeWindow doesn't always work http://code.google.com/p/xmonad/issues/detail?id=375 It seems that scaling a window down always work, but scaling up often fails. Here's my relevant keybinding: , ("M-<KP_Left>", withFocused (keysResizeWindow (-10, 0) (1%2, 1%2))) , ("M-<KP_Right>", withFocused (keysResizeWindow (10, 0) (1%2, 1%2))) , ("M-<KP_Up>", withFocused (keysResizeWindow (0, 10) (1%2, 1%2))) , ("M-<KP_Down>", withFocused (keysResizeWindow (0, -10) (1%2, 1%2))) I tested the operations on Google Chrome, Emacs, and urxvt: All four work on Chrome. M-U and M-R fail on urxvt; M-L and M-D work. M-U fail on Emacs; others work. What version of the product are you using? On what operating system? Darcs. Arch. Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". Please provide any additional information below. Attachments: xmonad.hs 9.1 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

recompile, dzen and togglestruts
by julien steinhauser 22 Feb '10

22 Feb '10

Hello, On a fresh XMonad setup, I meet an issue and I'd like wise advices, wether I'm doing things correctly or not. I use two dzen, one for views, layout and title on the left and one for other things on right. The one on left is launched from within xmonad.hs via spawnpipe the one on right is lauched from my .xinitrc. If i make a change in xmonad.hs and want to recompile it, it compiles silently (no output with xmonad --recompile). All clients which were already here before the recompile won't cover the left dzen anymore after the recompile even with the mod-b shortcut (dzen stays on top) but they still cover the dzen on the right. All clients launched after the recompile behave the normal way, until I recompile ... My xmonad version : ~$ xmonad --version xmonad 0.9.1 (Source package xmonad and xmonad-contrib from Debian Sid) I attach my xmonad.hs I hope this message wasn't too confused. Julien

1 2