June 2007 - xmonad - Haskell.org

Issue 14 in project xmonad
by codesite-noreply＠google.com 05 Jun '07

05 Jun '07

Issue 14: Workspace information to stdout http://code.google.com/p/xmonad/issues/detail?id=14 Comment #4 by dons00: This feature has been implemented. When the internal state of xmonad changes, and Config.logging = True, a Haskell representation of the window manager state is printed to stdout. This is to be used in conjunction with scripts that would parse the output, and, for example, hand it to dzen. Users should try this out. Issue attribute updates: Status: Fixed Labels: Milestone-Release0.3 -- 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

contrib patch: nicer tiled layout obeying size hints
by Peter De Wachter 05 Jun '07

05 Jun '07

These two layouts mimic the default ones, but they obey size hints while trying to avoid gaps between windows. (But I'm thinking it might be nice to have a uniform 1 pixel gap...)

2 1

darcs patch: Contrib package for 6.4 users
by daniel＠wagner-home.com 04 Jun '07

04 Jun '07

Mon Jun 4 15:55:34 PDT 2007 daniel(a)wagner-home.com * Contrib package for 6.4 users

2 1

Issue 6 in project xmonad
by codesite-noreply＠google.com 04 Jun '07

04 Jun '07

Issue 6: Xmonad does not respect size hints http://code.google.com/p/xmonad/issues/detail?id=6 Comment #6 by SpencerJanssen: xmonad now obeys size hints for floating windows. 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

updated size hints patch
by Peter De Wachter 04 Jun '07

04 Jun '07

This version of the patch applies cleanly to current darcs xmonad and adds support for floating windows. I've recorded the tiling windows part and the floating window part in different patches, so you can apply only one and not the other. The gaps in tiled mode are still there.

3 2

Issue 6 in project xmonad
by codesite-noreply＠google.com 04 Jun '07

04 Jun '07

Issue 6: Xmonad does not respect size hints http://code.google.com/p/xmonad/issues/detail?id=6 Comment #5 by pdewacht: GTK programs (libgtk 2.10.12) in floating mode don't like being resized to a size that doesn't fit their size hints. They first snap back to their original size, then resize themselves to an approximation that fits their hints. This causes ugly flicker, as shown on the attached animated gif. Attachments: gnome-terminal.gif 44.4 KB -- 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: realign guard
by l.mai＠web.de 04 Jun '07

04 Jun '07

Mon Jun 4 20:20:45 CEST 2007 l.mai(a)web.de * realign guard

1 0

Howtos wanted: Configuring xmonad with display managers
by Jason Creighton 04 Jun '07

04 Jun '07

Hi, I keep running into people on #xmonad or #haskell who are trying to configure, eg, gdm to run xmonad. I've never run a display manger, so I have no clue how to help them. I think it would be great if we had a page that listed most popular display manger type configurations, and how to set up xmonad in them. Is anybody running [xgk]dm with xmonad? If so, how? Please post your answer here, stating what distro you're running (is anybody running xmonad on something other than Linux?) and we'll compile the answers and put them up on the webpage. Or maybe there needs to be an xmonad wiki or something. In any case, this seems to be a hurdle that lots of people are hitting, and I think we should try to make it as easy as possible to run xmonad. Jason Creighton

11 13

State information, workspace names and "emptyness" indicator
by Robert Manea 04 Jun '07

04 Jun '07

Hi, below you'll find a _rather hackish_ approach to display state information with xmonad. See the comments in the script to get it running. Here is a shot how it could look like, note the upper left corner: http://omploader.org/file/xmonad-dzen-state-wsnames.png Script and instructions: #!/usr/bin/perl # statedump.pl - beware, hackish solution # # (c) 2007 by Robert Manea <rob dot manea at gmail dot com> # dump xmonad state in a readable format # # Usage: # ------ # Uncomment the line reading "withWindowSet (io . hPrint stderr)" # in xmonad's Operations.hs. This will enable a state dump. # # start xmonad like this: # xmonad 2>&1 | statedump.pl | dzen2 -w 300 -ta l # # Workspaces containing windows have an * prefix # the current workspace is enclosed in [ ] # use strict; use warnings; #---------------------------------------------------------------------- # set the names of the workspaces # if no name is set, the workspace # number will be displayed my %ws2name = ( 0 => "dev", 1 => "mail", 2 => "web", 3 => "comm", 4 => "ham", 5 => "tmp" ); #---------------------------------------------------------------------- my $fr=0; $|=1; while(<>) { my @s = split /Workspace/; $s[1] =~ /tag\s=\s+W\s([0-9]),/; my $cws = $1; for(sort @s) { my @f = /{tag\s=\s+W\s([0-9]),.*stack\s=\s+(.*)/; my $ws = $f[0]; my $emp = $f[1]; $fr++; if($fr < @s) { print "*" if($emp !~ /Empty/); if($ws eq $cws) { $ws2name{"$cws"} ? print '[', $ws2name{"$cws"}, '] ' : print '[', $cws+1, '] '; } else { $ws2name{"$ws"} ? print $ws2name{"$ws"}, ' ' : print $ws+1, ' '; } } } $fr=0; print "\n"; } __END Bye, Rob.

1 0

border colours
by Bruce Stephens 04 Jun '07

04 Jun '07

I note that normalBorderColor is a grey, and focusedBorderColor is red. I don't find these particularly distinguishable. Likely that's because I'm in the 10% or so of men who have red-green colour blindness (I believe it's normally the red receptor that's missing). Not a big deal, since this is easily changed. But maybe there's some alternative that would be acceptable to almost everyone? I find focusedBorderColor = "#ff00ff" to be nicely visible. Maybe it's too obvious?

3 3