May 2007 - xmonad - Haskell.org

Issue 9 in project xmonad
by codesite-noreply＠google.com 29 May '07

29 May '07

Issue 9: 'amarok' (KDE music program) causes reproducible failures from xmonad. http://code.google.com/p/xmonad/issues/detail?id=9 Comment #3 by SpencerJanssen: We can't reproduce this issue, and the initial reporter has not given sufficient detail. Closing for now. Issue attribute updates: Status: Invalid -- 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

Config.hs: version Config.hs.template instead?
by David Glasser 28 May '07

28 May '07

Can we delete Config.hs from the repository and version a Config.hs.template instead? (Part of the build process could be to copy the template onto the real file if it doesn't exist yet.) That way it's easy to hack on xmonad and customize your own experience with the same checkout. (And you can even version Config.hs in your own repository and just never push any patches to Config.hs, if I understand darcs correctly.) --dave -- David Glasser | glasser(a)mit.edu | http://www.davidglasser.net/

2 1

Darcs best practice: Resolving conflicts
by Jason Creighton 28 May '07

28 May '07

Hi guys, Dave Glasser and I recently both ran into an issue with darcs trying to merge patches with changes made locally. (Mine were unrecord; I think Dave's were recorded but unpushed patches.) Appearently, this may be due in part to conflicts in the main repo. It turns out that if you resolve conflicts the wrong way, you can end up with "merger" patches in the main repo that can cause problems later. I don't really understand that bit at all. But anyway, I talked to Heffalump on #darcs about this, and what I took away from the conversation was this: Whenever you have conflicts between two recorded patches, you should use amend-record to fix the conflict instead of making a separate "fix conflicts" patch. You can't use amend-record on any patch that has been released into the wild: only patches that have never left your local repo. If the conflicts are between a patch and unrecorded local changes, my understanding is that it's fine to just fix the conflicts in the files and then record. Disclaimer from Heffalump: 11:43 <jcreigh> Heffalump++ Thanks for all your help. 11:44 <jcreigh> I'm going to kick an email out to the xmonad ML warning people about the proper way to resolve conflicts, because at least myself was unaware, so possibly others. 11:44 <Heffalump> I don't think it's widely known. 11:45 <Heffalump> you should probably qualify it as not being advice from someone who is core to darcs development Disclaimer from me: The above is my understanding of the situation. I could be wrong. Hopefully David Roundy will be kind enough to chime in if that is the case. Jason Creighton

1 0

darcs patch: Windows on multiple workspaces
by Robert Marlow 28 May '07

28 May '07

Sat May 26 17:16:17 JST 2007 Rob <bobstopper(a)bobturf.org> * Windows on multiple workspaces Previously, it was a invariant that a window will never have duplicates in the stackset. This invariant has been removed and replaced with the invariant that a window will never have duplicates in a stack. It may have duplicates appear in other stacks. This makes it possible to have DWM style tagging. Other than adjusting insertLeft and delete/deleteAll to allow for duplicates in the stackset, support must be made for xinerama. The xinerama support is designed as follows: 1. The current screen always has all windows showing. This ensures that focus (only meaningful on the current screen) will not need to be changed 2. non-current visible screens have all windows showing which are not already showing on windows to the screen's "left" (defined as screens with lower ordered identifiers). This functionality has been placed in a new visibleOnScreen function which returns the windows visible on a screen given the above rules. The refresh and hide functions in Operations have been adjusted to use this new function to ensure windows are displayed sanely.

3 4

Popup status bar support
by dons＠cse.unsw.edu.au 28 May '07

28 May '07

Proper support for a popup statusbar has been added -- a whole 1 line needed rewriting :-) Assuming you have something like dzen[1] running, say as: while true ; do date ; sleep 30 ; done \ | dzen2 -ta r -fg '#a8a3f7' -bg '#3f3c6d' -p & Which displays a 15 pixel high status bar at the top of the screen, you'd edit your Config.hs, change defaultStatusGap from 0 to 15, and reload. mod-b will then toggle on or off the status bar. Screenshots: http://www.cse.unsw.edu.au/~dons/code/xmonad-web/images/screen-rob-status-s… http://www.cse.unsw.edu.au/~dons/code/xmonad-web/images/screen-dons-status.… The 'gap' is just a pixel gap, so you could put any permanent (or pop up) content in that gap. Any client that ignores the window manager would be suitable to use as a 'status bar'. By the way, the 'gap' height for a given font is calculable using the script in utils/gapcalc.c, courtesy of Rob, dzen's creator. -- Don 1. http://gotmor.googlepages.com/dzen

3 4

Unusual tiling/tesselation ideas, anyone?
by dons＠cse.unsw.edu.au 27 May '07

27 May '07

I'm interested in seeing if there are some other unexplored tiling algorithms out there, we could try out. Fib spiral tiling seems one option. There must be some other cool ones (just start at http://en.wikipedia.org/wiki/Tessellation) There's a lot of research on plane tiling we could just adopt directly. Anyone want to write a few interesting ones? It would be neat to have xmonad be a testbed for novel tiling interface design, due to its simple pure layout system. -- Don

2 5

darcs patch: Generate keybindings section in manpage from Config.hs
by Jason Creighton 27 May '07

27 May '07

Sun May 27 00:29:14 MDT 2007 Jason Creighton <jcreigh(a)gmail.com> * Generate keybindings section in manpage from Config.hs

1 0

darcs patch: replace "name" in NamedWindow with a Show instance.
by David Roundy 27 May '07

27 May '07

Sat May 26 11:51:14 PDT 2007 David Roundy <droundy(a)darcs.net> * replace "name" in NamedWindow with a Show instance.

2 1

darcs patch: tagging windows with multiple workspaces
by Robert Marlow 27 May '07

27 May '07

Sat May 26 17:33:18 JST 2007 bobstopper(a)bobturf.org * tagging windows with multiple workspaces

2 2

Issue 9 in project xmonad
by codesite-noreply＠google.com 27 May '07

27 May '07

Issue 9: 'amarok' (KDE music program) causes reproducible failures from xmonad. http://code.google.com/p/xmonad/issues/detail?id=9 Comment #2 by dons00: stepcut uses amarok 1.4.4-4+b1, and reports it has worked from before 0.1 was released, through to today's head version. Works launched using dmenu, or via xterm. Will require more information from original submitter, or others to reproduce it. Issue attribute updates: Status: Started -- 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