- xmonad - Haskell.org

[dzen] dzen gadget: dbar
by Robert Manea 29 Jun '07

29 Jun '07

Hi, here is another simple gadget that you can use in combination with dzen. It is a general purpose progressbar, perfectly suited to be used inside your scripts, that displays the piped in values numerically and in a semi graphical way. Options: -m : Value to be considered 100% (default: 100) -w : Number of charcaters to be considered 100% in the bar (default: 25 ) -s : Symbol represeting the percentage value in the bar (default: = ) -l : label to be prepended to the bar (default: '' ) Usage examples: 1) If your 100% mark changes dynamically: echo "50 150" | dbar ^ ^ | |__ max. value | |__ value to display Output: 33% [======== ] 2) Static 100% mark: echo 25 | dbar -m 100 -l Sometext Output: Sometext 25% [====== ] 3) Multiple runs: for i in 2 20 50 75 80; do echo $i; sleep 1; done | dbar | dzen2 Output: Find out yourself. Have fun, Rob.

1 0

darcs patch: flexible resizing for floating windows
by l.mai＠web.de 28 Jun '07

28 Jun '07

Fri Jun 29 00:49:24 CEST 2007 l.mai(a)web.de * flexible resizing for floating windows

3 2

trouble with xmonad on OS X
by Ben Weaver 28 Jun '07

28 Jun '07

Hello, I've just installed xmonad on OS X, but I'm having trouble running it. When I start X11 and type "xmonad" into the terminal this error is returned: xmonad: fatal error: request code=2, error code=10 Error: BadAccess (attempt to access private resource denied) I'm running these software versions: * OS X 10.4.10/ppc on a Powerbook G4 * Apple's X11.app (1.1.3 -- XFree86 4.4.0) * ghc 6.6.1, installed from macports * X11-extras 0.2, installed manually * xmonad 0.2, installed manually Could this be Xinerama-related? I have a second display attached to my laptop, but I've tried running xmonad without the second display attached and it fails with the same error message. When I configured the X11-extras package, these warnings were generated (although it build successfully): checking X11/extensions/Xinerama.h usability... no checking X11/extensions/Xinerama.h presence... yes configure: WARNING: X11/extensions/Xinerama.h: present but cannot be compiled configure: WARNING: X11/extensions/Xinerama.h: check for missing prerequisite headers? configure: WARNING: X11/extensions/Xinerama.h: see the Autoconf documentation configure: WARNING: X11/extensions/Xinerama.h: section "Present But Cannot Be Compiled" configure: WARNING: X11/extensions/Xinerama.h: proceeding with the preprocessor's result configure: WARNING: X11/extensions/Xinerama.h: in the future, the compiler will take precedence checking for X11/extensions/Xinerama.h... yes If it helps, here is the console.log snippet generated when starting X11 console.log ========= XFree86 Version 4.4.0 / X Window System (protocol Version 11, revision 0, vendor release 6600) [DRI] screen 0 installation complete Screen 0 added: 2304x1024 @ (0,0) Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! Any help is appreciated. Best wishes, -Ben

2 1

darcs patch: move Spiral to LayoutHelpers. (and 4 more)
by David Roundy 28 Jun '07

28 Jun '07

A resend for dons. Conflicts with two recently accepted patches, but I don't see that as my fault. If you accept patches that implement wrong fixes for code written my myself that I've properly fixed, then you can deal with the conflicts. David Sat Jun 23 07:35:16 PDT 2007 David Roundy <droundy(a)darcs.net> * move Spiral to LayoutHelpers. Sat Jun 23 07:35:42 PDT 2007 David Roundy <droundy(a)darcs.net> * introduce idModify which is just "const (return Nothing)". Sat Jun 23 07:37:45 PDT 2007 David Roundy <droundy(a)darcs.net> * move Accordian to use idModify. Sat Jun 23 14:09:52 PDT 2007 David Roundy <droundy(a)darcs.net> * make everything work with new doLayout. This modifies all the contrib modules to work (so far as I know) with the new contrib layout. The exception is the LayoutHooks module, which isn't used. It exports an API that is inherently unsafe, so far as I can tell (and always has been). Sun Jun 24 10:13:46 PDT 2007 David Roundy <droundy(a)darcs.net> * clean up code in Combo. This adds some type safety, since the super-layout is now of a distinct type from the sublayouts. This avoids the ugliness we had, of passing "fake" windows to the super layout. Now we directly lay out the layouts.

3 8

Issue 30 in xmonad: Dragging windows across screens does not switch the window's workspace
by codesite-noreply＠google.com 27 Jun '07

27 Jun '07

Issue 30: Dragging windows across screens does not switch the window's workspace http://code.google.com/p/xmonad/issues/detail?id=30 Comment #2 by jcreigh: Fixed in darcs 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

darcs patch: Change a window's workspace when dragging across scree...
by Jason Creighton 27 Jun '07

27 Jun '07

Wed Jun 27 20:50:23 MDT 2007 Jason Creighton <jcreigh(a)gmail.com> * Change a window's workspace when dragging across screens (closes #30)

2 1

Rechecking XMonad with Catch
by Neil Mitchell 27 Jun '07

27 Jun '07

Hi, With the patch I recently submitted, Yhc can now compile StackSet with the pattern guards. Using the latest Yhc (from darcs), and the latest Catch (0.1.1 from Hackage, recently updated): There are 5 incomplete patterns, 2 are proven safe. All the 3 unsafe ones are in "new". Taking a closer look, you are allowing any Integral method to be passed, which includes those who have really wacky semantics. Restricting this to Int there are 6 incomplete patterns, 5 are proven safe. The remaining one should be proven safe by Catch, if the initial transformation stage hadn't obfustcated something. I am confident I can fix Catch to fix this, and will do so for Catch 0.2. The exact problem is that let's are not floated inside case's currently, but should be. Thanks Neil

1 0

darcs patch: simplify StackSet.delete (and 1 more)
by David Roundy 27 Jun '07

27 Jun '07

Hi Don, Here's a fix to make filter use the same semantics as delete. There are no properties for filter, and it's only used once, to remove the floating windows from the stack before tiling them, and in this one case, I believe the ideal semantics--for tiling algorithms that are focus-dependent--would be to match the semantics of delete, so that if the floating window that currently has the focus is deleted the tiling of the tiled layer won't change. That seems most reasonable to me. David Sun Jun 24 07:48:54 PDT 2007 David Roundy <droundy(a)darcs.net> * simplify StackSet.delete Wed Jun 27 06:40:51 PDT 2007 David Roundy <droundy(a)darcs.net> * fix filter semantics to match delete.

1 0

darcs patch: support self-modifying layouts.
by David Roundy 27 Jun '07

27 Jun '07

A resend for dons. Sat Jun 23 13:14:47 PDT 2007 David Roundy <droundy(a)darcs.net> * support self-modifying layouts.

2 1

darcs patch: Note that SimpleStacking is incompatible with Xinerama
by Jason Creighton 27 Jun '07

27 Jun '07

Tue Jun 26 21:54:26 MDT 2007 Jason Creighton <jcreigh(a)gmail.com> * Note that SimpleStacking is incompatible with Xinerama It's unclear to me what SimpleStacking is supposed to accomplish, so I'm just going to note that it doesn't work with Xinerama. (Due to assuming that the current workspace is the one being laid out)

3 4