- xmonad - Haskell.org

xmonad community: charts and graphs
by dons＠cse.unsw.edu.au 21 Jun '07

21 Jun '07

100 day of xmonad! Here's some info on what's happening with the project. Charts and (pie!) graphs. The community and project are looking quite healthy. Good work everyone! Contributors to the core xmonad, in terms of patches: http://www.cse.unsw.edu.au/~dons/images/xmonad-core-contrib-07-06-21.png Contributors to the contrib library: http://www.cse.unsw.edu.au/~dons/images/xmonad-extentsions-contrib-07-06-21… Commit rate to core: http://www.cse.unsw.edu.au/~dons/images/commits/community/xmonad-commits.png Commit rate to extensions library: http://www.cse.unsw.edu.au/~dons/images/commits/community/XMonadContrib-com… Mailing list traffic growth (currently 91 subscribed): http://gmane.org/plot-rate.php?group=gmane.comp.lang.haskell.xmonad (see dwm: http://gmane.org/plot-rate.php?group=gmane.comp.window-managers.dwm ion: http://gmane.org/plot-rate.php?group=gmane.comp.window-managers.ion.general Last week in the irc channel (new record 48 users): http://irc.netsplit.de/tmp/channels/712_1001858.png Keep up the good work everyone. -- Don

1 0

Issue 28 in xmonad: status bar windows shouldn't be movable
by codesite-noreply＠google.com 21 Jun '07

21 Jun '07

Issue 28: status bar windows shouldn't be movable http://code.google.com/p/xmonad/issues/detail?id=28 Comment #3 by dons00: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- 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 28 in xmonad: status bar windows shouldn't be movable
by codesite-noreply＠google.com 21 Jun '07

21 Jun '07

Issue 28: status bar windows shouldn't be movable http://code.google.com/p/xmonad/issues/detail?id=28 Comment #2 by avi.rozen: Confirmed. Also verified that dzen2 recieves mouse events it's meant to recieve. Thanks. -- 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

patch: Make Magnifier's master window behavior customizable
by Peter De Wachter 21 Jun '07

21 Jun '07

* Make Magnifier's master window behavior customizable based on a suggestion by Tim Hobbs

3 3

darcs patch: Main.hs: get rid off non-standard patter... (and 4 more)
by joachim.fasting＠gmail.com 21 Jun '07

21 Jun '07

Tue Jun 19 00:25:30 CEST 2007 joachim.fasting(a)gmail.com * Main.hs: get rid off non-standard pattern guards. Use nested case statements when creating the winset binding. Looks _really_ ugly, compared to the original, and adds 3 loc. Tue Jun 19 05:43:42 CEST 2007 joachim.fasting(a)gmail.com * Xmonad.whenX: flip instead of lambda abstraction. Wed Jun 20 17:35:41 CEST 2007 joachim.fasting(a)gmail.com * Operations.hs: redundant parens. Wed Jun 20 18:59:51 CEST 2007 joachim.fasting(a)gmail.com * Remove use of ';' to circumvent layout rules. This adds about 3 loc, but using ';' is cheating anyways. Wed Jun 20 19:08:33 CEST 2007 joachim.fasting(a)gmail.com * XMonad.hs: minor cosmetic code tweaks.

4 7

darcs patch: Main.hs: get rid off non-standard pattern guards.
by joachim.fasting＠gmail.com 21 Jun '07

21 Jun '07

Thu Jun 21 00:04:21 CEST 2007 joachim.fasting(a)gmail.com * Main.hs: get rid off non-standard pattern guards. Adds another import and looks a bit convoluted, but this is the best I could do. Also, any trailing non-numeric characters (as in --resume 9r) will be ignored, as this code just blindly calls fst if reads returns anything but an empty list (don't know if this is stupid or not).

2 1

Issue 28 in xmonad: status bar windows shouldn't be movable
by codesite-noreply＠google.com 21 Jun '07

21 Jun '07

Issue 28: status bar windows shouldn't be movable http://code.google.com/p/xmonad/issues/detail?id=28 Comment #1 by dons00: The problem was that mouse events weren't checked to ensure they were only on a managed window. We now do so, which appears to fix the issue. Pleae verify and confirm. See patch: Thu Jun 21 11:17:00 EST 2007 Don Stewart <dons(a)cse.unsw.edu.au> * only perform mouse events on managed windows. closes #28 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 28 in xmonad: status bar windows shouldn't be movable
by codesite-noreply＠google.com 20 Jun '07

20 Jun '07

Issue 28: status bar windows shouldn't be movable http://code.google.com/p/xmonad/issues/detail?id=28 New issue report by avi.rozen: What steps will reproduce the problem? 1. launch xmonad with the dzen2 status bar (using run-xmonad.sh) 2. move status bar with mod-click and mouse What is the expected output? What do you see instead? status bar should not move, but it does (run-xmonad.sh actually launches two instances of dzen2, which can be moved independently) What version of the product are you using? On what operating system? latest (21 Jun 07) darcs repository (xmonad and X11-extras), Debian "lenny" x86 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: use a Layout to set the Screen rectangles.
by David Roundy 20 Jun '07

20 Jun '07

Hi all, Here's a moderate-sized change that might be controversial. I've replaced xineScreens with a screenLayout that calls into Xinerama to get the screen rectangles. This has a couple of potential advantages. One is that we could use this to move the gap treatment into XMonadContrib, or at least out of XState, as we no longer require a special data structure to store the gaps: it could just be a very simple Layout modifier. I believe this would simplify the core even if we don't move it entirely into XMonadContrib (which is what I'd do, figuring that core should be only things that either everyone needs or are both trivially small and something that everyone needs *one* of. It also (and this is why I wrote this) allows (with a separately sent XMonadContrib module) those of us who only have one screen to pretend we've got more than one screen. So all developers can test and see how things will behave (e.g. sticky-window code) under Xinerama. And it also gives users the ability to get something like a version of Combo that works with tabs, and sort of emulates sticky windows. I don't think it'd really a long-term solution to either of those UI goals, but in the interim, it's better than nothing. It might even be enough to get me to upgrade at work to the latest xmonad (I've been sticking with the one where Combo worked). Anyhow, this is the first application of the more general Layout type. It expands the code a little bit, but if we use it to simplify gap handling, that might be enough to compensate. David P.S. To reiterate, I think that the ability to test Xinerama behavior easily is enough to make this patch worthwhile, particularly since that seems to be a primary goal of xmonad, and it makes it tricky for those of us who don't have that possibility to make changes to xmonad core that will be acceptable. e.g. many of us want sticky windows, but we hear that it'll be hard with Xinerama, but folks with multiple screens don't seem to care, presumably because they've already got sticky workspaces. Wed Jun 20 06:36:03 PDT 2007 David Roundy <droundy(a)darcs.net> * use a Layout to set the Screen rectangles. An accompanying patch will allow those of us with only one physical screen to divide it into virtual screens at runtime.

2 4

darcs patch: Whitespace.
by joachim.fasting＠gmail.com 20 Jun '07

20 Jun '07

Wed Jun 20 13:58:52 CEST 2007 joachim.fasting(a)gmail.com * Whitespace.

2 1