- xmonad - Haskell.org

Issue 137 in xmonad: Incorrectly specified BorderColor brings down xmonad on restart
by codesite-noreply＠google.com 06 Feb '08

06 Feb '08

Issue 137: Incorrectly specified BorderColor brings down xmonad on restart http://code.google.com/p/xmonad/issues/detail?id=137 Comment #3 by dons00: This issue has been fixed in the darcs branch of xmonad. The patch of interest is: {{{ Wed Feb 6 11:48:58 PST 2008 Don Stewart <dons(a)galois.com> * Lift initColor exceptions into Maybe }}} Thanks for the report. Issue attribute updates: Status: Fixed -- 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 137 in xmonad: Incorrectly specified BorderColor brings down xmonad on restart
by codesite-noreply＠google.com 06 Feb '08

06 Feb '08

Issue 137: Incorrectly specified BorderColor brings down xmonad on restart http://code.google.com/p/xmonad/issues/detail?id=137 Comment #2 by dons00: (No comment was entered for this change.) Issue attribute updates: Owner: dons00 -- 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 137 in xmonad: Incorrectly specified BorderColor brings down xmonad on restart
by codesite-noreply＠google.com 06 Feb '08

06 Feb '08

Issue 137: Incorrectly specified BorderColor brings down xmonad on restart http://code.google.com/p/xmonad/issues/detail?id=137 Comment #1 by dons00: Confirmed. Work is underway to fix this. Issue attribute updates: Status: Accepted Labels: -Priority-Medium Priority-Critical Milestone-Release0.7 -- 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

NMU done
by Joachim Breitner 06 Feb '08

06 Feb '08

Hi Ian, I am doing an NMU upload of version 1.4.1 – I think our users have waited long enough. I uploaded it to the 7-day delayed queue[1], in case you want to prepare a better package until then. I did no do any changes to the .diff.gz besides updating the changelog: $ interdiff haskell-x11_1.3.0-1.diff haskell-x11_1.4.1-0.1.diff -p 1 diff -u haskell-x11-1.3.0/debian/changelog haskell-x11-1.4.1/debian/changelog --- haskell-x11-1.3.0/debian/changelog +++ haskell-x11-1.4.1/debian/changelog @@ -1,3 +1,10 @@ +haskell-x11 (1.4.1-0.1) unstable; urgency=low + + * New upstream release (Closes: 454440) + * NMU upload to get xmonad 0.6 into Debian + + -- Joachim Breitner <nomeata(a)debian.org> Mon, 04 Feb 2008 16:56:52 +0100 + haskell-x11 (1.3.0-1) unstable; urgency=low * New upstream version. I did not try to fix and bugs already present in 1.3.0. Thanks for your packaging work and I hope there is no bad personal reason for the delay of your work. I will upload xmonad 0.6 to the NEW queue very shortly. A note to users that had my local .nomeata3 version of haskell-x11 installed: The just uploaded version will not be automatically installed, but it should be identical anyways. Once a real maintainer upload will happen (1.4.1-1), it will be automatically installed again. Greetings, Joachim [1] http://people.debian.org/~djpig/delayed/haskell-x11_1.4.1-0.1_i386.changes -- Joachim "nomeata" Breitner Debian Developer nomeata(a)debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nomeata(a)joachim-breitner.de | http://people.debian.org/~nomeata

2 4

Issue 137 in xmonad: Incorrectly specified BorderColor brings down xmonad on restart
by codesite-noreply＠google.com 06 Feb '08

06 Feb '08

Issue 137: Incorrectly specified BorderColor brings down xmonad on restart http://code.google.com/p/xmonad/issues/detail?id=137 New issue report by semdornus: What steps will reproduce the problem? 1. Change the normalBorderColor or focusedBorderColor in your configuration - i.e. normalBorderColor = "000" (note missing "#"). 2. Restart xmonad with the standard modm-q binding. What is the expected output? What do you see instead? Expected: xmonad keeps running with the old configuration and displays an error message about the problem. Actual: xmonad crashes with "user error (error in allocNamedColor)" What version of the product are you using? On what operating system? darcs | gentoo 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

Issue 136 in xmonad: Better documentation for layout combinators
by codesite-noreply＠google.com 05 Feb '08

05 Feb '08

Issue 136: Better documentation for layout combinators http://code.google.com/p/xmonad/issues/detail?id=136 New issue report by gotmor: While the layout combinators look really powerful and set xmonad aside of other tiling WMs the docs are absolutly incomprehensible (at least for me and possibly for many non-haskellers). I'd imagine a descrition what all the '*/**' stuff actually stands for and ma few step by step examples that set up some layouts and make use of as much functionality of the layout combinators as possible. If this error is due to a module from XMonadContrib, please tag this issue with 'Component-Contrib' below. Component-Contrib 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: Add windowRemover for make tabbed return just the focu...
by Andrea Rossato 05 Feb '08

05 Feb '08

Hi, this is a follow up of the discussion with Spencer about tabbed. This patch implements WindowRemover. If placed over tabbed it should be removing unfocused windows, without touching the windows decoration. WARNING: while this patch passes all tests both with ghc-6.6.1 and ghc-6.8.2, when I build this test file: import XMonad import XMonad.Config.Arossato main = xmonad =<< arossatoConfig ghc-6.6.1 fails with this linker error: [12:00:33][wolf@laptop:~/.xmonad]$ ghc --make xmonad.hs Linking xmonad ... /usr/local/lib/xmonad-contrib-0.6/ghc-6.6.1/libHSxmonad-contrib-0.6.a(Combo.o): In function `s1e0s_info': ghc3557_0.hc:(.text+0x3ada): undefined reference to `xmonadzmcontribzm0zi6_XMonadziLayoutziWindowNavigation_zdf3_info' /usr/local/lib/xmonad-contrib-0.6/ghc-6.6.1/libHSxmonad-contrib-0.6.a(Combo.o):(.rodata+0xa8): undefined reference to `xmonadzmcontribzm0zi6_XMonadziLayoutziWindowNavigation_zdf3_closure' collect2: ld returned 1 exit status The same code compiles, and works perfectly (unless bugs introduced by its author, me) on ghc-6.8.2. This is why I'd like someone to test it (I'll include it also in the bug tracker). Cheers, Andrea Fri Feb 1 11:55:05 CET 2008 Andrea Rossato <andrea.rossato(a)unibz.it> * Add windowRemover for make tabbed return just the focused window

6 19

darcs patch: Run.hs: add an option to runinterms (and 1 more)
by gwern0＠gmail.com 05 Feb '08

05 Feb '08

Mon Feb 4 22:18:24 EST 2008 gwern0(a)gmail.com * Run.hs: add an option to runinterms It turns out that for urxvt, and most terminal, apparently, once you give a '-e' option, that's it. They will not interpret anything after that as anything but input for /bin/sh, so if you wanted to go 'runInTerm "'screen -r session' -title IRC"', you were SOL - the -title would not be seen by urxvt. This, needless to say, is bad, since then you can't do stuff like set the title which means various hooks and extensions are helpless. This patch adds an extra options argument which is inserted *before* the -e. If you want the old behaivour, you can just go 'runInTerm "" "executable"', but now if you need to do something extra, 'runInTerm "-title mutt" "mutt"' works fine. This patch also updates callers. Mon Feb 4 22:21:55 EST 2008 gwern0(a)gmail.com * +doc for WindowGo.hs: I've discovered a common usecase for me for raiseMaybe

1 0

Trying to code jump-or-execute
by Joseph Garvin 05 Feb '08

05 Feb '08

I'm a former sawfish user, and I used to have this really awesome keyboard shortcut called "jump-or-exec". I would press for example Super+F, and if Firefox was not running, it would be executed, and if it was already running, then it would be given focus. I had similar shortcuts for emacs, terminals, etc. I'm a bit of a haskell newb -- I can tell that I can simply use 'spawn' to launch a process, and if I had a list of current windows I would know how to iterate through them and find out whether one currently exists, but I don't know how to get such a list. Ideally I'd like to be able to match against window title or class. Is there a way to do this with xmonad?

8 8

[dons@galois.com: Re: More than 5 mouse buttons in Graphics.X11?]
by Friedrich Delgado Friedrichs 04 Feb '08

04 Feb '08

Hi! I'd really like to be able to ,((0, button6), withFocused W.swapMaster) (with EZConfig and additionalMouseBindings) See forwarded mail. -- Friedrich Delgado Friedrichs <friedel(a)nomaden.org> Laziness led to the invention of the most useful tools.

4 5