February 2008 - xmonad

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

07 Feb '08

Issue 137: Incorrectly specified BorderColor brings down xmonad on restart http://code.google.com/p/xmonad/issues/detail?id=137 Comment #5 by dons00: Thanks for responding. I'll take a look at this. We may be dropping the defaults somewhere. We can also report a more interesting error. -- 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 07 Feb '08

07 Feb '08

Issue 137: Incorrectly specified BorderColor brings down xmonad on restart http://code.google.com/p/xmonad/issues/detail?id=137 Comment #4 by semdornus: Thanks for the fix. There is indeed no crash anymore. Two small caveats though; there is no xmessage specifying the problem, which could confuse the user ("Why doesn't my new configuration work?") and make any problem hunting in the configuration itself troublesome. Secondly I use a spawnPipe (dzen2) with DynamicLog for the workspaces, etc. This doesn't work anymore in combination with this problem. If I restart with an incorrect bordercolor dzen2 doesn't come up anymore. -- 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

New Xmonad user
by Arturo Borquez 07 Feb '08

07 Feb '08

Hi all, (please forgive me, my mother tounge is spanish, so be patient). I've successfully instaled xmonad and xmobar on a FREEBSD-6.3. I have done my key bindings, and a nice status bar for xmobar. Xmonad is really nice and productive (as I dislike the mouse). I come from Ion WM, and I want to change the Mod1 (ALT key) by the Control key. if it is possible please tell me how it could be done. Best Regards Arturo Borquez ____________________________________________________________________________________ ¡Capacidad ilimitada de almacenamiento en tu correo! No te preocupes más por el espacio de tu cuenta con Correo Yahoo!: http://correo.espanol.yahoo.com/

2 1

XMonad 0.5, combo layouts, swapDown and swapUp
by Dave Harrison 07 Feb '08

07 Feb '08

Hey all, First up, love the new configuration method, my xmonad.hs file is now nice and tiny :-) Quick "maybe glitch" though, I'm using ComboLayout with Tabbed, and I find that when I first add lots of windows to the layout the alt-tab order is correct (also when adding windows into the middle of the stack it's correct). When I swapDown or swapUp _in_ the stack, the order is correct. But if I swapDown or swapUp at either end of the stack the ordering goes rather pearshaped (the ordering is no longer correct "visually" if you see what I mean). Is this a known thing ? My xmonad.hs is below. Cheers, Dave ---- import XMonad hiding (Tall(..)) import qualified XMonad.StackSet as W import XMonad.Layout.Tabbed import XMonad.Layout.Combo import XMonad.Layout.TwoPane import XMonad.Layout.NoBorders import XMonad.Layout.HintedTile import XMonad.Config (defaultConfig) import XMonad.Hooks.DynamicLog import XMonad.Util.Dmenu import qualified Data.Map as M import System.IO (hPutStrLn) daveConfig = defaultConfig { defaultGaps = [(0,15,0,0)] , logHook = dynamicLog , terminal = "xterm -fa Mono -fs 12" , layoutHook = smartBorders ( combineTwo (TwoPane 0.03 0.5) (tabbed shrinkText defaultTConf) (tabbed shrinkText defaultTConf) ||| mytab ||| tiled Tall ||| tiled Wide ||| Full ) , keys = \c -> mykeys c `M.union` keys defaultConfig c } where -- layouts tiled = HintedTile 1 0.03 0.5 mytab = tabbed shrinkText defaultTConf -- key mapping overrides mykeys (XConfig {modMask = modm, workspaces = ws}) = M.fromList $ [((modm, xK_Left ), sendMessage Shrink) -- %! Shrink the master area ,((modm, xK_Right ), sendMessage Expand) -- %! Expand the master area ,((modm, xK_p ), spawn "exe=`cat /home/dave/.dmenulist | dmenu -b -p \"$\"` && eval \"exec $exe\"") -- @@ Launch dmenu ] main = xmonad $ daveConfig

5 9

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

07 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 07 Feb '08

07 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 07 Feb '08

07 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 07 Feb '08

07 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 06 Feb '08

06 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