[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xmonad
Subject:    Re: [xmonad] Issue 433 in xmonad: Alternative Implementation of
From:       Yaakov M Nemoy <loupgaroublond () gmail ! com>
Date:       2011-02-11 20:56:53
Message-ID: 20110211205653.GC20521 () warp ! hexago ! nl
[Download RAW message or body]

Hey,

I came across some issues recently with DynamicWorkspaces and
WorkspaceDir. When i create a new workspace, WD seems to sometimes
forget which dir the other workspaces were using. I was considering
implementing exactly this solution :D.

I'm all for this. +1.

-Yaakov

On Fri, Feb 11, 2011 at 07:53:22AM +0000, codesite-noreply@google.com wrote:
> Status: New
> Owner: ----
> 
> New issue 433 by que...@gmail.com: Alternative Implementation of
> WorkspaceDir
> http://code.google.com/p/xmonad/issues/detail?id=433
> 
> Hey, I just extracted an alternative implementation of WorkspaceDir
> from my configuration and was wondering what the opinion on this is.
> Could it go into contrib as alternative? Is it better or worse than
> the original?
> 
> It's using ExtensibleState to map WorkspaceIds to directories. It
> also provides a method to execute action that get the current
> directory as parameter to access the information.
> There is no need to modify any layouts with this version.
> 
> Regards,
> Jan
> 
> Attachments:
> 	WorkspaceDir.hs  3.1 KB
> 
> 
> _______________________________________________
> xmonad mailing list
> xmonad@haskell.org
> http://www.haskell.org/mailman/listinfo/xmonad

_______________________________________________
xmonad mailing list
xmonad@haskell.org
http://www.haskell.org/mailman/listinfo/xmonad
[prev in list] [next in list] [prev in thread] [next in thread]