October 2007 - xmonad

Issue 64 in xmonad: floating windows change size after being moved.
by codesite-noreply＠google.com 19 Oct '07

19 Oct '07

Issue 64: floating windows change size after being moved. http://code.google.com/p/xmonad/issues/detail?id=64 Comment #1 by byorgey: Additionally, when I open The Gimp (which automatically gets put in the floating layer via manageHook), one of the windows opens at a normal size but then immediately changes size continuously until it is extremely tall and skinny (only 1 icon wide). Attempting to resize this window works until I release the mouse button, at which point it jumps back to being tall and skinny. If I set borderWidth=0, this problem does not occur. -- 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 64 in xmonad: floating windows change size after being moved.
by codesite-noreply＠google.com 19 Oct '07

19 Oct '07

Issue 64: floating windows change size after being moved. http://code.google.com/p/xmonad/issues/detail?id=64 New issue report by byorgey: What steps will reproduce the problem? 1. Make sure borderWidth > 0. 2. Open a new window and pull it into the floating layer. 3. Resize or drag the window. What is the expected output? What do you see instead? The window appears to jump up and to the left and also shrink slightly. Experiments with the borderWidth indicate that the amount of movement/shrinking are determined by the borderWidth. What version of the product are you using? On what operating system? Bleeding-edge darcs, on GNU/Linux (Ubuntu feisty). 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

Combo layouts ??
by Dave Harrison 19 Oct '07

19 Oct '07

Hi all, I've just been trying to use Combo to setup a two-pane split workspace, but the examples in the contrib file don't work for me. When I use this line, combo (TwoPane 0.03 0.5) [(Full,1),(tabbed shrinkText defaultTConf,1)] in my Config.hs as follows, layouts = [ combo (TwoPane 0.03 0.5) [(Full,1),(tabbed shrinkText defaultTConf,1)] , Layout $ tabbed shrinkText defaultTConf , Layout tiled , Layout $ Mirror tiled , Layout Full ] I get the following build error, Preprocessing executables for xmonad-0.4... Building xmonad-0.4... [ 6 of 15] Compiling Config[boot] ( Config.hs-boot, nothing ) [14 of 15] Compiling Config ( Config.hs, dist/build/xmonad/xmonad-tmp/Config.o ) Config.hs:139:39: Couldn't match expected type `Layout a' against inferred type `Full a1' In the expression: Full In the expression: (Full, 1) In the second argument of `combo', namely `[(Full, 1), (tabbed shrinkText defaultTConf, 1)]' What am I doing wrong here ?? Cheers, Dave

5 8

patch: update UrgencyHook documentation
by Brent Yorgey 19 Oct '07

19 Oct '07

A small update to the UrgencyHook documentation, to make it correspond to the newest WindowNavigation and Config.hs.

2 1

darcs patch: -Wall police
by l.mai＠web.de 19 Oct '07

19 Oct '07

Thu Oct 18 05:30:00 CEST 2007 l.mai(a)web.de * -Wall police

2 1

xmonad does not start
by Alexander Solovyov 19 Oct '07

19 Oct '07

Hi, I hope you can help me. I've compiled xmonad step by step as written in manual, but it does not start - after logging in xdm my screen just blink several times (like X restarting - and it restarts, according to log) and shows starting screen again. My distro is ALT Linux (I think this does not matter ;)), GHC 6.6.1, all libraries was installed by distro except X11-extras (which I have installed in my home, just like xmonad itself). Maybe I can provide some more precise information? Just say what I need to tell. Thanks in advance! Hope I'll have possibility to enjoy this great wm. :) -- Alexander

2 1

Agaginst LayoutModifiers for hooks
by Joachim Breitner 19 Oct '07

19 Oct '07

Hi, 0.4 is out, and I’m bringing up my old issue: Hooks. I quote the docs for the recent UrgencyHook extension: > Change your defaultLayout such that > withUrgencyHook is applied along the chain. Mine, for example: > > > defaultLayout = Layout $ withUrgencyHook $ windowNavigation wnConfig $ > > LayoutSelection defaultLayouts > > It shouldn't hurt to have the "withUrgencyHook $" at the outermost layer, > as above, as UrgencyHook is a LayoutModifier, and hence passes on any > messages sent to it. Is this really what we want our users to go through just so that they can add a simple extension? And what do urgency hooks have to do with Layouts? Wouldn’t this be much nicer: > Add urgencyHook to your xmonadHook list: > > > xmonadHooks = [ urgencyHook > , otherHooksYouAlreadyHave > ] > I will, in this post, leave out any discussion on how to implement this. Instead, I’d like to talk about the _user interface_ of adding extensions. Do you think we should make adding extensions easier for the user? How should registering extensions work in the configuration file? My suggestion is that there should be just one list, xmonadHooks (or xmonadExtensions, to further hide details from the user), where extensions are added. Options are just passed along, so for example: > -- User option for the UrgencyHook extension: > > urgencyAction window = do print "Something is urgent" > > > xmonadHooks = [ urgencyHook urgencyAction > , otherHooksYouAlreadyHave > ] Any comments on that? Greetings, Joachim -- Joachim Breitner e-Mail: mail(a)joachim-breitner.de Homepage: http://www.joachim-breitner.de ICQ#: 74513189

4 6

patch: give WindowNavigation an empty description
by Brent Yorgey 19 Oct '07

19 Oct '07

Hi all, The WindowNavigation layout modifier was using the default "show" as its description, leading to a lengthy mess when displaying the current layout (using e.g. DynamicLog). This patch changes the description to be empty, the reasoning being that I know whether I'm using WindowNavigation or not and don't need to see it in front of the layout. I've also included a small change to LayoutModifier so that an extra space is not added before the layout description when the modifier description is empty. -Brent

3 2

Issue 63 in xmonad: Control+a is lost when using controlMask for workspace switching.
by codesite-noreply＠google.com 19 Oct '07

19 Oct '07

Issue 63: Control+a is lost when using controlMask for workspace switching. http://code.google.com/p/xmonad/issues/detail?id=63 Comment #2 by SpencerJanssen: The problem is that we bind keys [xK_1..] to workspaces, and the user had 18 workspaces defined. xK_A = xK_1 + 16. We now limit the workspace keys to [xK_1 .. xK_9] by default. 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 63 in xmonad: Control+a is lost when using controlMask for workspace switching.
by codesite-noreply＠google.com 19 Oct '07

19 Oct '07

Issue 63: Control+a is lost when using controlMask for workspace switching. http://code.google.com/p/xmonad/issues/detail?id=63 Comment #1 by SpencerJanssen: I can't reproduce this bug. Have you made any other changes to Config.hs? -- 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