November 2009 - xmonad

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: 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 310 in xmonad: XMonad.Main.handle eats WM_NAME property changes
by codesite-noreply＠google.com 07 Feb '10

07 Feb '10

Updates: Status: Accepted Labels: Type-Defect Component-Core Comment #1 on issue 310 by byorgey: XMonad.Main.handle eats WM_NAME property changes http://code.google.com/p/xmonad/issues/detail?id=310 I can reproduce this. Could a core developer take a look at this? If it is really as easy as amdragon suggests (and the suggested fix wouldn't be undesirable for other reasons), this ticket has no excuse for still being open. =) -- 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

Call for xmonad.hs
by Gwern Branwen 17 Jan '10

17 Jan '10

Hi everyone. So a while ago we were discussing how to improve defaults and what sorts of types and functions XM and XMC could provide which encapsulate common behavior, when Devon asked me what exactly I saw being repeated (besides the 2 or 3 examples I provided), and it occurred to me that I really didn't know. There're ~30 xmonad.hs's here <http://haskell.org/haskellwiki/Xmonad/Config_archive>, but perhaps 1/3 to 1/2 are obsolete or don't compile with darcs XM/XMC (at a very rough guess). I'd like more. So here's what I would greatly appreciate everyone doing: 1) Upload your config 2) If you've uploaded your config, update it! 3) If you use someone else's config, why not mention it? I'd appreciate knowing who's using what, so I can count the popular configurations proportionately* 4) If you don't want to do any of 1-3, perhaps you could email me privately with your config? Thanks in advance all. * I think it's fair to say that if 10 people are using a particular xmonad.hs, and there's a simplification which could be made, that change should count 10x -- gwern ANZUS nuclear Lebed .ch Domination .tm top Amherst USSS Hugo

10 27

Issue 335 in xmonad: Manual workspace sorting mode using extensible state
by codesite-noreply＠google.com 30 Dec '09

30 Dec '09

Status: Accepted Owner: ---- Labels: Type-Enhancement Priority-Low Component-Contrib New issue 335 by byorgey: Manual workspace sorting mode using extensible state http://code.google.com/p/xmonad/issues/detail?id=335 In addition to the automatic workspace sorting functions in X.U.WorkspaceCompare, it would be nice to have another module providing a "manual workspace sorting mode" which remembers a desired workspace order using extensible state, provides keybindings to reorder workspaces, and provides hooks to use the current ordering with things like DynamicLog and CycleWS. I'll code this up myself eventually, but since I don't have time right at the moment I thought I'd post it as an enhancement in case some other enterprising hacker(s) feel like tackling it before I get around to it. -- 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

darcs patch: X.L.MouseResizableTile: keep draggers on the bottom of...
by Tomas Janousek 23 Dec '09

23 Dec '09

Hello, skimming through byorgey's bug swipe, I noticed that #207 applies to MouseResizableTile as well. Thu Nov 26 18:34:13 CET 2009 Tomas Janousek <tomi(a)nomi.cz> * X.L.MouseResizableTile: keep draggers on the bottom of the window stack. Regards, -- Tomáš Janoušek, a.k.a. Liskni_si, http://work.lisk.in/

4 4

Re: Issue 312 in xmonad: [improvement] MosaicAlt: change tall/wide
by codesite-noreply＠google.com 21 Dec '09

21 Dec '09

Updates: Status: Accepted Labels: Type-Enhancement Component-Contrib Comment #2 on issue 312 by byorgey: [improvement] MosaicAlt: change tall/wide http://code.google.com/p/xmonad/issues/detail?id=312 (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 3

New DarcsWatch features
by Joachim Breitner 21 Dec '09

21 Dec '09

Hi, if you follow planet.haskell.org you’ll have read that I attended the Darcs hacking sprint in Vienna. Together with the Darcs guys I integrated DarcsWatch better into their patch submission and review process. Let me outline it quickly * Darcs patches are sent to patches(a)darcs.net. * A new ticket (of type patch, not issue) is automatically created in their roundup instance. * The patch, with a reference to the ticket number, is sent by roundup to the darcs-users mailing list. * DarcsWatch is subscribed to that list and notices this mail as usual. * DarcsWatch detects the roundup patch tracker URL in the mail and remembers it. * It also sets a special "darcswatchurl" property of the roundup ticket (via e-Mail), to add a link to DarcsWatch on the roundup ticket view. * When the patch is eventually applied, DarcsWatch sends a mail to the roundup ticket, setting its state to "applied". A message about this is sent to the darcs-user list. This is not directly applicable to xmonad, of course. But due to the re-organization of the DarcsWatch code some new possibilities arise: 1. DarcsWatch could send bundle-applied-mails to the mailing list. Since patch submissions are on the list, this would we useful for people just following development. Also the submitter is likely happy to hear that his patch has been applied, without checking the repository or DarcsWatch. OTOH it would slightly increase the noise level on the list. 2. Users can subscribe to bundle-applied-mails about their own patches. It would be relatively easy to implement that I can give DarcsWatch a list of e-Mail-Adresses that want “Your bundle α was applied to repository β” notifications. This would be independent of xmonad, of course. Is anyone interested? I’d start with manually configuring the list with addresses people tell me about, and maybe later add an automatic subscription feature, if there is demand. 3. DarcsWatch could be integrated closer in the xmonad bug tracker. Of course, code.google.com will not be as easily hackable as a self-hosted roundup instance, but maybe some interaction is possible. Is there an API for that? Some features that are desirable are: * DarcsWatch should somehow be aware of patches submitted via code.google.com that were not sent to the mailing list. * DarcsWatch could be able to amend the ticket with the patch application status. * DarcsWatch could close tickets if a patch bundle is applied – but what if the patch does not work, if there are multiple patches etc.? The Darcs team has clearer semantics there, as patches and issues are tracked separately on roundup (but can refer to each other). Especially item 3 is meant to be a discussion starter :-) Greetings, Joachim -- Joachim "nomeata" Breitner mail: mail(a)joachim-breitner.de | ICQ# 74513189 | GPG-Key: 4743206C JID: nomeata(a)joachim-breitner.de | http://www.joachim-breitner.de/ Debian Developer: nomeata(a)debian.org

4 8

Changing module headers
by Gwern Branwen 20 Dec '09

20 Dec '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 So I mentioned a while ago I meant to go over XMC using the 'sim' tool (with an invocation like sim_mira `find . -name "*.hs"` - I discovered recently that it had Miranda support, which means quasi-Haskell support). But the results are littered with comments. Particularly obnoxious are the module headers, in part because they all seem to use '--' comments even if they cover dozens of lines. Would anyone object if I were to edit those to use {- -} style (and push those edits without review)? - -- gwern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREKAAYFAko+xRkACgkQvpDo5Pfl1oJuNwCgi4IhXrPLMdOHlWdReKTcMH2f GbUAn0pT7fM9dnLYW0acoaQrVKc2H51w =ngUp -----END PGP SIGNATURE-----

5 9

Issue 323 in xmonad: Config template refers to the removed 'dynamicLogDzen' function
by codesite-noreply＠google.com 17 Dec '09

17 Dec '09

Status: Accepted Owner: ---- Labels: Priority-High Component-Core Documentation New issue 323 by vogt.adam: Config template refers to the removed 'dynamicLogDzen' function http://code.google.com/p/xmonad/issues/detail?id=323 What steps will reproduce the problem? Check the configs here for dynamicLogDzen: http://haskell.org/haskellwiki/Xmonad/Config_archive/Template_xmonad.hs_%28… http://code.haskell.org/xmonad/man/xmonad.hs That commented function has been removed: see http://haskell.org/haskellwiki/Xmonad/Notable_changes_since_0.8#DynamicLog http://xmonad.org/xmonad-docs/xmonad-contrib/XMonad-Hooks-DynamicLog.html What is the expected output? What do you see instead? This misleads users. With what should the comment be replaced? What version of the product are you using? On what operating system? xmonad-contrib-0.9 -- 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