From codesite-noreply at google.com Fri Jun 1 00:06:38 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Fri Jun 1 00:02:18 2007 Subject: [Xmonad] Issue 14 in project xmonad Message-ID: <163600cefd0431d0578646a36972@google.com> Issue 14: Workspace information to stdout http://code.google.com/p/xmonad/issues/detail?id=14 Comment #2 by dglasser: Idea: whenever windowset (or maybe any field of XState) is changed, write out a representation of it to standard output. Then we can do xmonad | format-output | dzen2 or for that matter pipe it to a program which multiplexes output to multiple dzen2s on different screens. -- 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 From glasser at mit.edu Fri Jun 1 00:11:33 2007 From: glasser at mit.edu (glasser@mit.edu) Date: Fri Jun 1 00:07:15 2007 Subject: [Xmonad] darcs patch: Note that my xinerama patch is now in dzen. Message-ID: Fri Jun 1 00:11:12 EDT 2007 glasser@mit.edu * Note that my xinerama patch is now in dzen. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/x-darcs-patch Size: 5602 bytes Desc: A darcs patch for your repository! Url : http://www.haskell.org/pipermail/xmonad/attachments/20070601/64607ec5/attachment.bin From glasser at mit.edu Fri Jun 1 00:39:18 2007 From: glasser at mit.edu (glasser@mit.edu) Date: Fri Jun 1 00:34:58 2007 Subject: [Xmonad] darcs patch: New contrib module: run internal xmonad commands via d... Message-ID: Fri Jun 1 00:38:49 EDT 2007 glasser@mit.edu * New contrib module: run internal xmonad commands via dmenu -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/x-darcs-patch Size: 8701 bytes Desc: A darcs patch for your repository! Url : http://www.haskell.org/pipermail/xmonad/attachments/20070601/bc62b174/attachment.bin From dons at cse.unsw.edu.au Fri Jun 1 00:45:33 2007 From: dons at cse.unsw.edu.au (Donald Bruce Stewart) Date: Fri Jun 1 00:41:17 2007 Subject: [Xmonad] darcs patch: New contrib module: run internal xmonad commands via d... In-Reply-To: References: Message-ID: <20070601044533.GA32475@cse.unsw.EDU.AU> glasser: > Fri Jun 1 00:38:49 EDT 2007 glasser@mit.edu > * New contrib module: run internal xmonad commands via dmenu Both applied. This one is quite nice: adds an interpreter for xmonad events. -- Don From dons at cse.unsw.edu.au Fri Jun 1 01:12:49 2007 From: dons at cse.unsw.edu.au (Donald Bruce Stewart) Date: Fri Jun 1 01:08:32 2007 Subject: [Xmonad] User-specified monad transformers Message-ID: <20070601051249.GB32475@cse.unsw.EDU.AU> Extensions will likely need state, or other abilities, not provided currently by the X monad core. One approach to solve this is to add a cheap symbol table to the XState field, allowing extensions to stick their own modifiable global state. A more intriguing, and perhaps, dangerous, idea, is to allow arbitrary monad transformers to be specified by user contributions. The problem of adding state then becomes a matter of defining a StateT transformer. But it also opens up the option of using ReaderT for config values, or even hmm, ContT for check pointing state (!). By default the outer monad would be IdentityT. Downsides are unexplored, the main being: * how do you combine state, or monad state, from multiple extensions? There are cheap solutions, as we see above, but the idea of user customised monad transformers -- redefining the entire application's behaviour -- is very tempting. Here's the patch for user-specified UserT transformers, to ponder. New patches: [User-definable monad transformers: most general state/behaviour extension we can think of Don Stewart **20070601050546] { hunk ./Config.hs 30 +import IdentityT hunk ./Config.hs 146 +------------------------------------------------------------------------ + +-- default monad transformer to run xmonad in: +type UserT = IdentityT + +-- default way to run the monad transformer +runUserT :: Monad m => UserT m a -> m a +runUserT = runIdentityT + +-- Example, user defined state: +-- type UserT = StateT () +-- runUserT m = evalStateT m () + hunk ./Config.hs-boot 2 +import IdentityT hunk ./Config.hs-boot 8 +runUserT :: Monad m => UserT m a -> m a +type UserT = IdentityT addfile ./IdentityT.hs hunk ./IdentityT.hs 1 +----------------------------------------------------------------------------- +-- | +-- Module : Identity.hs +-- Copyright : (c) Spencer Janssen 2007 +-- License : BSD3-style (see LICENSE) +-- +-- Maintainer : dons@cse.unsw.edu.au +-- Stability : stable +-- Portability : portable +-- +module IdentityT where + +import Control.Monad.Trans + +-- +-- IdentityT , a parameterisable identity monad, with an inner monad +-- The user's default monad transformer +-- + +newtype IdentityT m a = IdentityT { runIdentityT :: m a } + +instance (Functor m, Monad m) => Functor (IdentityT m) where + fmap f = IdentityT . fmap f . runIdentityT + +instance (Monad m) => Monad (IdentityT m) where + return = IdentityT . return + m >>= k = IdentityT $ runIdentityT . k =<< runIdentityT m + fail msg = IdentityT $ fail msg + +instance (MonadIO m) => MonadIO (IdentityT m) where + liftIO = IdentityT . liftIO hunk ./XMonad.hs 24 +import {-# SOURCE #-} Config (UserT, runUserT) hunk ./XMonad.hs 73 -newtype X a = X (ReaderT XConf (StateT XState IO) a) +newtype X a = X (ReaderT XConf (StateT XState (UserT IO)) a) hunk ./XMonad.hs 79 -runX c st (X a) = runStateT (runReaderT a c) st >> return () +runX c st (X a) = runUserT (runStateT (runReaderT a c) st) >> return () } Context: [ignore numlock/capslock on mouse bindings Jason Creighton **20070601015137] [now we handle transients properly, and restack windows, refresh from focus is ok Don Stewart **20070601022329] [Rename withWorkspace to withWindowSet. glasser@mit.edu**20070601001325] [Revert accidental change to border color Spencer Janssen **20070531145509] [comments on why fullscreen tiling doesn't work with `implicit' floating Don Stewart **20070531090537] [clean up mouse code a bit Don Stewart **20070531085308] [first shot at a floating layer Jason Creighton **20070531044733 This is a first attempting at a floating layer: mod-button1: move window mod-button2: swapMaster mod-button3: resize window mod-t: make floating window tiled again Moving or resizing a window automatically makes it floating. Known issues: Hard to manage stacking order. You can promote a window to move it to the top, (which you can do with mod-button2) but it should be easier than that. Moving a window by dragging it to a different Xinerama screen does not move it to that workspace. Code is ugly. ] [remove LOC cap (but still print count after tests) Jason Creighton **20070531043417] [TAG 0.2 Spencer Janssen **20070531010004] Patch bundle hash: 864d7acd95d9f45379cef7d18919783971b243f0 From codesite-noreply at google.com Fri Jun 1 01:29:56 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Fri Jun 1 01:25:36 2007 Subject: [Xmonad] Issue 17 in project xmonad Message-ID: <163600d1030431d181745aff9675@google.com> Issue 17: User-definable X monad state type http://code.google.com/p/xmonad/issues/detail?id=17 Comment #1 by dons00: We have two proposed solutions: 1), standard dynamically checked symbol table in XState. Using a Map String Dynamic or similar, see [http://cse.unl.edu/~sjanssen/typekey.hs]. Used in Yi, notably, for data type extensions. Upside: we know it works. Downside: runtime checking, urgh. 2) user-specified StateT types. Add a data type parameter to X, defined in Config.hs. Upside: fully statically checked. Downside: combining state from separate plugins would require boilerplate (would it) 3) serious generalisation: arbitrary monad transformers. let the user plug and play whatever semantics they want. upside: ridiculously powerful generalisation. downside: type hell trying to combine separate monads in separate extensions. -- 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 From codesite-noreply at google.com Fri Jun 1 01:30:56 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Fri Jun 1 01:26:35 2007 Subject: [Xmonad] Issue 17 in project xmonad Message-ID: Issue 17: User-definable X monad state type http://code.google.com/p/xmonad/issues/detail?id=17 Comment #2 by dons00: See [http://www.haskell.org/pipermail/xmonad/2007-June/000476.html this post] for a patch providing arbitrary monad transformers. -- 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 From dons at cse.unsw.edu.au Fri Jun 1 02:01:03 2007 From: dons at cse.unsw.edu.au (Donald Bruce Stewart) Date: Fri Jun 1 01:56:46 2007 Subject: [Xmonad] darcs patch: first shot at a floating layer In-Reply-To: <20070531192706.GC23075@abridgegame.org> References: <20070531192706.GC23075@abridgegame.org> Message-ID: <20070601060103.GB468@cse.unsw.EDU.AU> droundy: > On Wed, May 30, 2007 at 10:53:54PM -0600, Jason Creighton wrote: > > Wed May 30 22:47:33 MDT 2007 Jason Creighton > > * first shot at a floating layer > > > > This is a first attempting at a floating layer: > > > > mod-button1: move window > > mod-button2: swapMaster > > mod-button3: resize window > > > > mod-t: make floating window tiled again > > > > Moving or resizing a window automatically makes it floating. > > > > Known issues: > > > > Hard to manage stacking order. You can promote a window to move it to the top, > > (which you can do with mod-button2) but it should be easier than that. > > Indeed, this is ugly, but I think the fix is easy, we just need to use the > old version of swapMaster (I don't recall its name) that moves the given > window to the top of the stack. Then the floating layer will behave like a > normal window manager in this regard: raising a window leaves the other > windows in the same stacking order. yes, i think we actually have to handle the floating layer in its own stack, so that it can be ordered and shuffled like a normal overlapping wm. > I hope you're thinking that once this is cleaner we can move the button > configuration out of Main and into Config? That'll make it both easier to > configure and easier to find. And the refactor which'll be needed should > also help with other features like adding tabs, either to float windows or > to a tiled workspace with tabbed layout. will happen soon, jason's working on it. > I'm with dons on the question of reorganization, a bit flag to indicate the > float layer is just ugly. And I still hope someday to be able to refactor > the float layer out of xmonad entirely and into XMonadContrib. We may not > want this refactor to actually happen, but I think the code should be > structured such that it can be done--it'll make for cleaner code and a more > powerful interface. agreed. the floating-ness at least has to move away from being interleaved with tiled windows -- that just doesn't let fullscreen tiling work very well with floating windows, since focus gets permuted strangely. -- Don From dons at cse.unsw.edu.au Fri Jun 1 02:01:49 2007 From: dons at cse.unsw.edu.au (Donald Bruce Stewart) Date: Fri Jun 1 01:57:31 2007 Subject: [Xmonad] darcs patch: first shot at a floating layer In-Reply-To: <20070531193501.GD23075@abridgegame.org> References: <20070531192706.GC23075@abridgegame.org> <20070531193501.GD23075@abridgegame.org> Message-ID: <20070601060149.GC468@cse.unsw.EDU.AU> droundy: > Another couple of ideas for the float layer: > > mod1-button2 should raise a window that's not at the top, but lower to the > very bottom one that's already on top. Otherwise it can be hard to find > obscured windows. But once this behavior is configurable, of course, this > change will be less critical. > > When dragging a window, I'd rather it was displayed is it'll be when I > release it. Currently the window is raised to the top while being dragged, > but then released at the current stacking level, with the result that you > can easily "lose" the window you're dragging, if you drop it under a larger > window. This change wouldn't prevent that loss, but would make it obvious, > since the window would be hidden when you drag it under the larger one. > Another solution would be to always raise windows when moving them. Yes, that's better behaviour. From dons at cse.unsw.edu.au Fri Jun 1 02:39:56 2007 From: dons at cse.unsw.edu.au (Donald Bruce Stewart) Date: Fri Jun 1 02:35:38 2007 Subject: [Xmonad] A plan for the floating layer In-Reply-To: <20070601001610.GL23075@abridgegame.org> References: <20070531091709.GK25344@cse.unsw.EDU.AU> <20070531235905.GA29032@jpc.example.com> <20070601001610.GL23075@abridgegame.org> Message-ID: <20070601063956.GA981@cse.unsw.EDU.AU> droundy: > On Thu, May 31, 2007 at 05:59:05PM -0600, Jason Creighton wrote: > > On Thu, May 31, 2007 at 07:17:09PM +1000, Donald Bruce Stewart wrote: > > > data Workspace i a = Workspace { tag :: !i > > > , tiled :: Stack a > > > , float :: Stack a } > > > > With that, you know which window has the focus in each layer, but how > > would you know which layer has focus? Also, you need to store the > > RationalRect with their x/y/w/h information somewhere. Are you thinking > > of retaining the "floating" map? Or float :: Stack (a, RationalRect)? > > What about something like: > > data Workspace i a = Parent { tag :: !i > , child :: Stack (Workspace a) } > | Workspace { tag :: !i > , thewindows :: Stack a } > > Then we can put two or more workspaces together, and the same set of > functions can be used to track focus, etc. This would naturally allow for > multiple sets of floating windows (sticky, etc). Maybe it's overkill, but > when I see the same problem come up again and again (screens each have a > single workspace focussed, "tiled" has a single window focussed, "float" > has a single window focussed, workspaces each have one of "tile" or "float" > subworkspace focussed, I think that reuse of code sounds like a good plan. > > Or maybe, if we didn't want arbitrary nesting, we'd want "what's visible on > a given screen" to be of type > > data ScreenContents i a = ScreenContents { tag :: !i > , thechildren :: Stack (Workspace a) > } > data Workspace i a = Workspace { tag :: !i > , thewindows :: Stack a } > > We'd reuse the same focus code we've already got. Either way (my approach > or dons' suggestion) we have to decide on how to deal with things like > window focus cycling (does it cycle through float and tiled windows > separately?) But my suggestion could lead to (I think) a more natural > replacement for the docking work, for example. A dock could be just > another Workspace, which might be visible on many or all of your > ScreenContents'. > > I can't see to the end of this idea, how it'd all work, but it seems like > the elegant direction to move. Of course, one would want to move > gradually. On the other hand, if dons (or someone else) came up with a way > to represent the nested workspace as a tree-like zipper, maybe everything > would suddenly become simpler. This sounds a lot like the zipper idea > coming back at us. Yes, the more I ponder it, the more two layers really appears to act like a 2 level tree zipper. Focus is the current node, in the current layer, on the current workspace. The new idea is the layer separating floating and tiled windows. Some ops would traverse both. i'll think more about this tonight. If we find the right data structure, the code, and the right UI, will follow. -- Don (practicing zen in the art of coding) From xmonad at cenderis.demon.co.uk Fri Jun 1 05:00:03 2007 From: xmonad at cenderis.demon.co.uk (Bruce Stephens) Date: Fri Jun 1 04:56:16 2007 Subject: [Xmonad] darcs patch: first shot at a floating layer In-Reply-To: <20070601031330.GI31292@cse.unsw.EDU.AU> (Donald Bruce Stewart's message of "Fri\, 1 Jun 2007 13\:13\:31 +1000") References: <20070531053230.GH25344@cse.unsw.EDU.AU> <20070531062218.GJ25344@cse.unsw.EDU.AU> <876468rapd.fsf@cenderis.demon.co.uk> <20070531204441.GG23075@abridgegame.org> <871wgwr8mp.fsf@cenderis.demon.co.uk> <20070601031330.GI31292@cse.unsw.EDU.AU> Message-ID: <877iqo123w.fsf@cenderis.demon.co.uk> dons@cse.unsw.edu.au (Donald Bruce Stewart) writes: [...] > I note that by explicitly unmanaging a window, and using float mode to > move it into the gap, you can set any client whatsoerver as sticky/ > statusbar: > > , ((modMask .|. shiftMask, xK_u ), withFocused unmanage) Ah, cool. That's probably what I want. From codesite-noreply at google.com Fri Jun 1 05:02:45 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Fri Jun 1 04:58:24 2007 Subject: [Xmonad] Issue 14 in project xmonad Message-ID: <163600d1030431d47a8476dafbfe@google.com> Issue 14: Workspace information to stdout http://code.google.com/p/xmonad/issues/detail?id=14 Comment #3 by dons00: Example code to log state changes to stdout / stderr is in the repo now. It prints the internal state as a haskell structure. you could read it, and hack it, with a simple haskell script, e.g.: {-# OPTIONS -fglasgow-exts #-} import Data.List import StackSet import XMonad unW (W n) = n main = do s <- readIO =<< getLine :: IO ( StackSet W Integer S ) let c = map ( unW . tag ) $ workspace (current s) ws = sort $ map ( unW . tag ) $ map workspace (visible s) ++ hidden s print c print ws 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 From xmonad at cenderis.demon.co.uk Fri Jun 1 05:06:57 2007 From: xmonad at cenderis.demon.co.uk (Bruce Stephens) Date: Fri Jun 1 05:02:38 2007 Subject: [Xmonad] darcs patch: first shot at a floating layer In-Reply-To: <20070601025130.GG31292@cse.unsw.EDU.AU> (Donald Bruce Stewart's message of "Fri\, 1 Jun 2007 12\:51\:30 +1000") References: <20070531053230.GH25344@cse.unsw.EDU.AU> <20070531062218.GJ25344@cse.unsw.EDU.AU> <876468rapd.fsf@cenderis.demon.co.uk> <20070601025130.GG31292@cse.unsw.EDU.AU> Message-ID: <873b1c11se.fsf@cenderis.demon.co.uk> dons@cse.unsw.edu.au (Donald Bruce Stewart) writes: [...] > clocks, status bars and so on, go in the per-screen `gap', an unmanged > region of the screen, on any (or all) borders. xmonad will ignore > clients in that area, that have override-redirect set on them. Right, but that feels like losing a chunk of a screen for something that's only occasionally of value. I was thinking of having gkrellm (or something similar) always visible, but perhaps (adjustably) translucent, in which case it could just overlay normal windows. Hence the idea of something like a floating layer. Now I think of it, I think I was talking past David Roundy. I think he's talking about windows he wants to be in multiple workspaces in the sense that they participate in the workspace layouts. In this case, at least, I *don't* want the windows to affect layout (which is why I was thinking in terms of the floating stuff). However, quite possibly it's not worth the complexity. I'm sure a one line status bar with dzen will be sufficient. Or even a GNOME (or KDE) panel, I guess, since those can also hide themselves (so wouldn't need much permanent space---just few pixels). [...] From rob.manea at googlemail.com Fri Jun 1 07:50:42 2007 From: rob.manea at googlemail.com (Robert Manea) Date: Fri Jun 1 07:46:25 2007 Subject: [Xmonad] [dzen] new release 0.3.0 Message-ID: <20070601115042.GA19414@deski.rob-home.homeip.net> Hello, this release features a redesign and results in less memory usage and dependencies. The use of (multi)threading was abandoned in favour of the more portable, faster and less memory hungry select() function. All of dzen's features and options should work as usual so the redisign is transparent to the user. Get it here: http://gotmor.googlepages.com/dzen2-0.3.0.tar.gz Bye, Rob. P.S.: The changes have been merged into svn trunk. From droundy at darcs.net Fri Jun 1 09:57:19 2007 From: droundy at darcs.net (David Roundy) Date: Fri Jun 1 09:53:15 2007 Subject: [Xmonad] darcs patch: first shot at a floating layer In-Reply-To: <20070601031330.GI31292@cse.unsw.EDU.AU> References: <20070531053230.GH25344@cse.unsw.EDU.AU> <20070531062218.GJ25344@cse.unsw.EDU.AU> <876468rapd.fsf@cenderis.demon.co.uk> <20070531204441.GG23075@abridgegame.org> <871wgwr8mp.fsf@cenderis.demon.co.uk> <20070601031330.GI31292@cse.unsw.EDU.AU> Message-ID: <20070601135715.GA23480@abridgegame.org> On Fri, Jun 01, 2007 at 01:13:31PM +1000, Donald Bruce Stewart wrote: > > Ah, but that's tricky for xinerama, as I understand it. Anyway, I was > > just suggesting one new layer per screen, so that doesn't feel huge. > > Admittedly, presumably it's conceptually a new kind of layer, which is > > bad. And maybe it's not worth it. > > > > My hunch is the right way to do this is to have some windows always > > present on a screen. I'm thinking of that in terms of something like > > the new floating layers, but maybe there's a cleaner way to do it. > > I note that by explicitly unmanaging a window, and using float mode to > move it into the gap, you can set any client whatsoerver as sticky/ > statusbar: > > , ((modMask .|. shiftMask, xK_u ), withFocused unmanage) I guess, it seems to me that the gap itself is a horribly ugly hack to work around the inflexibilty and lack of power in the layout algorithms of xmonad. The right way to create the gap (apart from Xinerama) would be to express it as a layout in some sort of a nested workspace, so that you could go into true full-screen mode, or have some layouts that don't include the status bar. I've never wanted a status bar, because I've never felt that my screen was too large in any direction. So I prefer to put information in a corner (e.g. xclock, which is also nicer to read--my eyes don't need to focus on it to tell the time), so that I can use all the width and height of my screen. But, of course, this kind of configuration requires actual window management, and the gap is just precisely a case of giving up on managing windows. Better to have a window manager that is sufficiently powerful to manage all the windows right. -- David Roundy http://www.darcs.net From dons at cse.unsw.edu.au Fri Jun 1 10:07:17 2007 From: dons at cse.unsw.edu.au (Donald Bruce Stewart) Date: Fri Jun 1 10:02:59 2007 Subject: [Xmonad] darcs patch: first shot at a floating layer In-Reply-To: <20070601135715.GA23480@abridgegame.org> References: <20070531053230.GH25344@cse.unsw.EDU.AU> <20070531062218.GJ25344@cse.unsw.EDU.AU> <876468rapd.fsf@cenderis.demon.co.uk> <20070531204441.GG23075@abridgegame.org> <871wgwr8mp.fsf@cenderis.demon.co.uk> <20070601031330.GI31292@cse.unsw.EDU.AU> <20070601135715.GA23480@abridgegame.org> Message-ID: <20070601140717.GA3267@cse.unsw.EDU.AU> droundy: > On Fri, Jun 01, 2007 at 01:13:31PM +1000, Donald Bruce Stewart wrote: > > > Ah, but that's tricky for xinerama, as I understand it. Anyway, I was > > > just suggesting one new layer per screen, so that doesn't feel huge. > > > Admittedly, presumably it's conceptually a new kind of layer, which is > > > bad. And maybe it's not worth it. > > > > > > My hunch is the right way to do this is to have some windows always > > > present on a screen. I'm thinking of that in terms of something like > > > the new floating layers, but maybe there's a cleaner way to do it. > > > > I note that by explicitly unmanaging a window, and using float mode to > > move it into the gap, you can set any client whatsoerver as sticky/ > > statusbar: > > > > , ((modMask .|. shiftMask, xK_u ), withFocused unmanage) > > I guess, it seems to me that the gap itself is a horribly ugly hack to work > around the inflexibilty and lack of power in the layout algorithms of > xmonad. The right way to create the gap (apart from Xinerama) would be to Oh, its not so bad. its pretty much precisely what the extended WM spec states window managers should do for docks and status bars -- leave an area unmanaged. > express it as a layout in some sort of a nested workspace, so that you > could go into true full-screen mode, or have some layouts that don't > include the status bar. yes, i do see how we could do this. > I've never wanted a status bar, because I've never felt that my screen was > too large in any direction. So I prefer to put information in a corner > (e.g. xclock, which is also nicer to read--my eyes don't need to focus on > it to tell the time), so that I can use all the width and height of my > screen. But, of course, this kind of configuration requires actual window > management, and the gap is just precisely a case of giving up on managing > windows. Better to have a window manager that is sufficiently powerful to > manage all the windows right. Time and code :-) we'll be refactoring for genericity for a while, i'd imagine, so we may end up with generic zippers of stacks. I'm happy to make xmonad the most generic, beautiful code base, just a matter of time and effort. An interesting aside, i note Anselm's not planning any significant changes to dwm, dwm is finished, only bugfixes and minor feature will be accepted which leaves xmonad with good room to fill out Xinerama handling, and notable extensions like a true fullscreen tiling mode, mirroring and so on. I think we can take a good piece of the wm market :-) -- Don From glasser at mit.edu Fri Jun 1 12:14:26 2007 From: glasser at mit.edu (glasser@mit.edu) Date: Fri Jun 1 12:10:05 2007 Subject: [Xmonad] darcs patch: XMonadContrib.Commands: for workspace and screen comma... Message-ID: Fri Jun 1 12:13:51 EDT 2007 glasser@mit.edu * XMonadContrib.Commands: for workspace and screen commands, leave out W/S tag -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/x-darcs-patch Size: 6272 bytes Desc: A darcs patch for your repository! Url : http://www.haskell.org/pipermail/xmonad/attachments/20070601/f41cea14/attachment.bin From sjanssen at cse.unl.edu Fri Jun 1 14:05:05 2007 From: sjanssen at cse.unl.edu (Spencer Janssen) Date: Fri Jun 1 14:01:28 2007 Subject: [Xmonad] darcs patch: XMonadContrib.Commands: for workspace and screen comma... In-Reply-To: References: Message-ID: <20070601130505.4513b940@localhost> On Fri, 01 Jun 2007 12:14:26 -0400 glasser@mit.edu wrote: > Fri Jun 1 12:13:51 EDT 2007 glasser@mit.edu > * XMonadContrib.Commands: for workspace and screen commands, leave > out W/S tag Applied, thanks. From xmonad at cenderis.demon.co.uk Fri Jun 1 14:10:16 2007 From: xmonad at cenderis.demon.co.uk (Bruce Stephens) Date: Fri Jun 1 14:05:55 2007 Subject: [Xmonad] Docks and things Message-ID: <87ira7k0l3.fsf@cenderis.demon.co.uk> Is XMonad intended to respect _NET_WM_WINDOW_TYPE_DOCK? I note that when I start applications like kicker, gkrellm, etc., (which xprop says have _NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_DOCK) they sort of get managed (xmonad gives them a suitable managed window, though often it's blank (because the application's drawn itself elsewhere)). Shouldn't xmonad just ignore such client windows? From nahoo82 at gmail.com Fri Jun 1 18:45:36 2007 From: nahoo82 at gmail.com (Ruben Porras) Date: Fri Jun 1 21:15:47 2007 Subject: [Xmonad] xinerama not working Message-ID: <1180737936.25290.4.camel@localhost> Hi, I'm having problems with the xinerama support. I follow the installation steps and I run autoreconfigure. The xmonad binary is also linked with libXinerama.so. Howeverer when I create the first window it spans along the two monitors. Appart from that xmonad looks great :D Thanks. From codesite-noreply at google.com Fri Jun 1 22:41:24 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Fri Jun 1 22:37:02 2007 Subject: [Xmonad] Issue 18 in project xmonad Message-ID: Issue 18: Support other task bar / dock properties? http://code.google.com/p/xmonad/issues/detail?id=18 New issue report by dons00: Investigate the _NET_WM_WINDOW_TYPE_DOCK property. Which is set by gkrellm, kicker et al. _NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_DOCK. Might be a way to get the gap for docs. Issue attributes: Status: Accepted Owner: dons00 Labels: Type-Enhancement 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 From dons at cse.unsw.edu.au Fri Jun 1 22:41:26 2007 From: dons at cse.unsw.edu.au (Donald Bruce Stewart) Date: Fri Jun 1 22:37:05 2007 Subject: [Xmonad] Docks and things In-Reply-To: <87ira7k0l3.fsf@cenderis.demon.co.uk> References: <87ira7k0l3.fsf@cenderis.demon.co.uk> Message-ID: <20070602024126.GB1293@cse.unsw.EDU.AU> xmonad: > Is XMonad intended to respect _NET_WM_WINDOW_TYPE_DOCK? I note that > when I start applications like kicker, gkrellm, etc., (which xprop > says have _NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_DOCK) they > sort of get managed (xmonad gives them a suitable managed window, > though often it's blank (because the application's drawn itself > elsewhere)). Shouldn't xmonad just ignore such client windows? Hmm, perhaps. I'd have to read the spec. We haven't looked at this yet. On the todo list. -- Don From jcreigh at gmail.com Fri Jun 1 22:54:28 2007 From: jcreigh at gmail.com (Jason Creighton) Date: Fri Jun 1 22:50:10 2007 Subject: [Xmonad] xinerama not working In-Reply-To: <1180737936.25290.4.camel@localhost> References: <1180737936.25290.4.camel@localhost> Message-ID: <20070602025428.GA537@jpc.example.com> On Sat, Jun 02, 2007 at 12:45:36AM +0200, Ruben Porras wrote: > Hi, > > I'm having problems with the xinerama support. I follow the installation > steps and I run autoreconfigure. The xmonad binary is also linked with > libXinerama.so. > > Howeverer when I create the first window it spans along the two > monitors. Appart from that xmonad looks great :D Hmm. The xmonad binary being linked to libXinerama.so would seem to indicate that X11-extras built with Xinerama support enabled. Weird. So let's try to figure this out, eh? Please give the versions that you are running of the following: xmonad X11-extras your X server What does this program output when you run it under X? import Graphics.X11.Xlib import Graphics.X11.Xinerama main = do d <- openDisplay "" xineramaQueryScreens d >>= print getScreenInfo d >>= print Jason Creighton From codesite-noreply at google.com Fri Jun 1 23:12:01 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Fri Jun 1 23:07:38 2007 Subject: [Xmonad] Issue 19 in project xmonad Message-ID: Issue 19: Investigate a way to allow contrib extensions to use compositing. http://code.google.com/p/xmonad/issues/detail?id=19 New issue report by dons00: Hooks, or basic, compositing support. Unsure how hard this is, or how useful. It seems though, with a little work, a tiling, compositing wm would probably take a big chunk of the tiling wm market. Drop shadows alone would be very nice. The potential does need investigating. Issue attributes: Status: Accepted Owner: dons00 Labels: Type-Enhancement 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 From dons at cse.unsw.edu.au Fri Jun 1 23:44:42 2007 From: dons at cse.unsw.edu.au (Donald Bruce Stewart) Date: Fri Jun 1 23:40:42 2007 Subject: [Xmonad] xinerama not working In-Reply-To: <1180737936.25290.4.camel@localhost> References: <1180737936.25290.4.camel@localhost> Message-ID: <20070602034442.GD1293@cse.unsw.EDU.AU> nahoo82: > Hi, > > I'm having problems with the xinerama support. I follow the installation > steps and I run autoreconfigure. The xmonad binary is also linked with > libXinerama.so. Can you check that X11-extras found and built with Xinerama support? Perhaps provide the configure logs for X11-extras. > Howeverer when I create the first window it spans along the two > monitors. Appart from that xmonad looks great :D Yes, a sure sign X11-extras didn't build with Xinerama. Usually this is due to the xinerama libs not being found by configure. -- Don From jcreigh at gmail.com Sat Jun 2 00:08:54 2007 From: jcreigh at gmail.com (Jason Creighton) Date: Sat Jun 2 00:04:34 2007 Subject: [Xmonad] darcs patch: make mouse bindings configurable Message-ID: Fri Jun 1 22:06:47 MDT 2007 Jason Creighton * make mouse bindings configurable -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/x-darcs-patch Size: 7987 bytes Desc: A darcs patch for your repository! Url : http://www.haskell.org/pipermail/xmonad/attachments/20070601/cf758f0a/attachment.bin From codesite-noreply at google.com Sat Jun 2 00:44:09 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Sat Jun 2 00:39:46 2007 Subject: [Xmonad] Issue 20 in project xmonad Message-ID: Issue 20: xrandr to make the resolution lesser does not update the geometry http://code.google.com/p/xmonad/issues/detail?id=20 New issue report by tim.thelion: What steps will reproduce the problem? 1. when the screen resolution is 1400x1050 do xrandr -s 1280x1024 2. then start firefox, 3. you will see that the right hand side is cut off What is the expected output? What do you see instead? That the geometry for firefox would be set correctly What version of the product are you using? On what operating system? 0.2 on Debian/GNU/Linux Please provide any additional information below. 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 From jcreigh at gmail.com Sat Jun 2 01:27:31 2007 From: jcreigh at gmail.com (Jason Creighton) Date: Sat Jun 2 01:23:13 2007 Subject: [Xmonad] darcs patch: only grab button{1, 2, 3} for click-to-focus (scrollwhee... Message-ID: Fri Jun 1 23:26:05 MDT 2007 Jason Creighton * only grab button{1,2,3} for click-to-focus (scrollwheel shouldn't focus) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/x-darcs-patch Size: 2192 bytes Desc: A darcs patch for your repository! Url : http://www.haskell.org/pipermail/xmonad/attachments/20070601/9c2f18ee/attachment.bin From wagnerd at stanford.edu Sat Jun 2 01:41:35 2007 From: wagnerd at stanford.edu (Daniel Wagner) Date: Sat Jun 2 01:37:10 2007 Subject: [Xmonad] darcs patch: first shot at a floating layer In-Reply-To: <1ea387f60705312022v291821cdu79a32bfa8f13f526@mail.gmail.com> References: <20070531053230.GH25344@cse.unsw.EDU.AU> <20070531062218.GJ25344@cse.unsw.EDU.AU> <876468rapd.fsf@cenderis.demon.co.uk> <20070601025130.GG31292@cse.unsw.EDU.AU> <1ea387f60705312022v291821cdu79a32bfa8f13f526@mail.gmail.com> Message-ID: <4661030F.3050101@stanford.edu> David Glasser wrote: > Excellent. The only downside to doing it this way is that to have > different bars on different windows, you'd have to make the output You shouldn't need to do any fancy multiplexing, or have different status bars on different workspaces. Just send a new line (that has the updated workspace number) to dzen's stdin. ~d From wagnerd at stanford.edu Sat Jun 2 02:33:04 2007 From: wagnerd at stanford.edu (Daniel Wagner) Date: Sat Jun 2 02:28:39 2007 Subject: [Xmonad] darcs patch: keybindings to warp pointer to window center Message-ID: <46610F20.6060506@stanford.edu> Fri Jun 1 23:31:27 PST 2007 Daniel Wagner * keybindings to warp pointer to window center -------------- next part -------------- New patches: [keybindings to warp pointer to window center daniel@wagner-home.com**20070602062328] { addfile ./Warp.hs hunk ./Warp.hs 1 +module XMonadContrib.Warp where + +{- Usage: + - This can be used to make a keybinding that warps the pointer to a given + - window or screen. For example, I've added the following keybindings to + - my Config.hs: + - + - , ((modMask, xK_z ), warpToWindow (1%2) (1%2)) -- @@ Move pointer to currently focused window + - + - -- mod-ctrl-{w,e,r} @@ Move mouse pointer to screen 1, 2, or 3 + - ++ + - [((modMask .|. controlMask, key), warpToScreen sc (1%2) (1%2)) + - | (key, sc) <- zip [xK_w, xK_e, xK_r] [0..]] + - + - Note that warping to a particular screen may change the focus. + -} + +import Data.Ratio +import Data.Maybe +import Control.Monad.RWS +import Graphics.X11.Xlib +import Graphics.X11.Xlib.Extras +import Operations +import XMonad + +fraction :: (Integral a, Integral b) => Rational -> a -> b +fraction f x = floor (f * fromIntegral x) + +ix :: Int -> [a] -> Maybe a +ix n = listToMaybe . take 1 . drop n + +warp :: Window -> Position -> Position -> X () +warp w x y = withDisplay $ \d -> io $ warpPointer d none w 0 0 0 0 x y + +warpToWindow :: Rational -> Rational -> X () +warpToWindow h v = + withDisplay $ \d -> + withFocused $ \w -> do + wa <- io $ getWindowAttributes d w + warp w (fraction h (wa_width wa)) (fraction v (wa_height wa)) + +warpToScreen :: Int -> Rational -> Rational -> X () +warpToScreen n h v = do + xScreens <- gets xineScreens + root <- asks theRoot + whenJust (ix n xScreens) $ \r -> + warp root (rect_x r + fraction h (rect_width r)) + (rect_y r + fraction v (rect_height r)) } Context: [Extract NamedWindow support from Mosaic into its own module glasser@mit.edu**20070523155855] [remove SwapFocus (which is no longer possible) David Roundy **20070523153841 This module depended on the focus stack. ] [Fix Spiral's module name Spencer Janssen **20070522170909] [[SPIRAL] add spiral tiling layout joe.thornber@gmail.com**20070522062537] [Make RotView compile. Miikka Koskinen **20070522075338 As I'm not a Xinerama user, I'm not sure if rotView should consider only hidden workspaces or also visible but not focused workspaces. I thought hidden workspaces only would be more logical. ] [bug fix in DwmPromote. whoops. Miikka Koskinen **20070522062118] [make FindEmptyWorkspace compile Miikka Koskinen **20070521123239] [make DwmPromote compile Miikka Koskinen **20070521123140] [updated Dmenu.hs to work with zipper StackSet Jason Creighton **20070521233947] [Add GreedyView Spencer Janssen **20070521220048] [Rescreen: collects new screen information Spencer Janssen **20070521164808] [Fixes for windowset -> workspace rename Spencer Janssen **20070521042118] [TwoPane: hide windows that aren't in view Spencer Janssen **20070518224240] [make Mosaic even less picky by default. David Roundy **20070516175554] [add clear window message in Mosaic. David Roundy **20070516175518] [Comment only Spencer Janssen **20070517211003] [Add instructions for TwoPane Spencer Janssen **20070517210206] [Add TwoPane Spencer Janssen **20070517195618] [throttle the exponential expense when many windows are present. David Roundy **20070516022123] [make mosaic configure windows by name rather than by Window. David Roundy **20070512215644 Note that this is still pretty flawed. Often window names change, and the layout then stagnates a bit. Gimp, for example, opens most its windows with the same name before renaming them, so you have to hit mod-return or something to force a doLayout. Also, gimp still overrides xmonad regarding the size of its main window. :( ] [XMonadContrib.FindEmptyWorkspace Miikka Koskinen **20070513184338 With this module you can find empty workspaces, view them and tag windows to them. ] [make DwmPromote compile Miikka Koskinen **20070513184254] [make DwmPromote compile again Miikka Koskinen **20070510154158] [make DwmPromote compile Miikka Koskinen **20070503105236] [add SwapFocus. David Roundy **20070512191315] [make rotView only consider non-visible workspaces (Xinerama) Jason Creighton **20070510012059] [fix commend in RotView. David Roundy **20070505185654] [switch to Message type for layout messages Don Stewart **20070505014332] [Fix instructions in Mosaic. Chris Mears **20070503222345] [add Mosaic layout. David Roundy **20070503151024] [-Wall police Spencer Janssen **20070503211700] [Make RotView build, and add a brief description. Chris Mears **20070503104234] [comment: Gave URL to xinerama-enabled dmenu patch Jason Creighton **20070503053133] [Put dmenu in X too Spencer Janssen **20070503053727] [Add dmenu (thanks jcreigh) Spencer Janssen **20070503052225] [add RotView module. David Roundy **20070421233838] [XMonadContrib.DwmPromote: dwm-like promote Miikka Koskinen **20070501082031 I like the way dwm's equivalent to xmonad's promote works, so I implemented dwmpromote. ] [add simple date example Don Stewart **20070429064013] [more details Don Stewart **20070429061426] [add readme Don Stewart **20070429061329] [Initial import of xmonad contributions Don Stewart **20070429061150] Patch bundle hash: e45f520b8209418b2358630d1587af1528af78b1 From sjanssen at cse.unl.edu Sat Jun 2 02:43:01 2007 From: sjanssen at cse.unl.edu (Spencer Janssen) Date: Sat Jun 2 02:38:55 2007 Subject: [Xmonad] Docks and things In-Reply-To: <87ira7k0l3.fsf@cenderis.demon.co.uk> References: <87ira7k0l3.fsf@cenderis.demon.co.uk> Message-ID: <20070602014301.54d6e6d1@localhost> On Fri, 01 Jun 2007 19:10:16 +0100 Bruce Stephens wrote: > Is XMonad intended to respect _NET_WM_WINDOW_TYPE_DOCK? I note that > when I start applications like kicker, gkrellm, etc., (which xprop > says have _NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_DOCK) they > sort of get managed (xmonad gives them a suitable managed window, > though often it's blank (because the application's drawn itself > elsewhere)). Shouldn't xmonad just ignore such client windows? xmonad is intentionally ignorant of EWMH hints like _NET_WM_WINDOW_TYPE_DOCK at the moment. We're considering using the _NET_WM_STRUT property to automatically manage windows as statusbars. Stay tuned for more info. Cheers, Spencer Janssen From codesite-noreply at google.com Sat Jun 2 02:49:10 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Sat Jun 2 02:44:46 2007 Subject: [Xmonad] Issue 20 in project xmonad Message-ID: <163600d1030431e6baa179ce32f22@google.com> Issue 20: xrandr to make the resolution lesser does not update the geometry http://code.google.com/p/xmonad/issues/detail?id=20 Comment #1 by SpencerJanssen: I'd like a bit more information: - What is the output of 'xdpyinfo | grep XINERAMA'? (ie. is the Xinerama extension active) - Does this problem remain with the darcs version of X11-extras? -- 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 From codesite-noreply at google.com Sat Jun 2 02:49:28 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Sat Jun 2 02:45:05 2007 Subject: [Xmonad] Issue 20 in project xmonad Message-ID: Issue 20: xrandr to make the resolution lesser does not update the geometry http://code.google.com/p/xmonad/issues/detail?id=20 Comment #2 by SpencerJanssen: (No comment was entered for this change.) Issue attribute updates: Owner: SpencerJanssen -- 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 From codesite-noreply at google.com Sat Jun 2 02:50:08 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Sat Jun 2 02:45:44 2007 Subject: [Xmonad] Issue 18 in project xmonad Message-ID: <163600d6850431e6be1412783320c@google.com> Issue 18: Support other task bar / dock properties? http://code.google.com/p/xmonad/issues/detail?id=18 Comment #1 by SpencerJanssen: Also, check _NET_WM_STRUT. Issue attribute updates: Cc: SpencerJanssen -- 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 From dons at cse.unsw.edu.au Sat Jun 2 03:05:19 2007 From: dons at cse.unsw.edu.au (Donald Bruce Stewart) Date: Sat Jun 2 03:00:58 2007 Subject: [Xmonad] darcs patch: keybindings to warp pointer to window center In-Reply-To: <46610F20.6060506@stanford.edu> References: <46610F20.6060506@stanford.edu> Message-ID: <20070602070519.GA2348@cse.unsw.EDU.AU> wagnerd: > Fri Jun 1 23:31:27 PST 2007 Daniel Wagner > * keybindings to warp pointer to window center Applied. Good work. -- Don From dons at cse.unsw.edu.au Sat Jun 2 03:23:10 2007 From: dons at cse.unsw.edu.au (Donald Bruce Stewart) Date: Sat Jun 2 03:18:48 2007 Subject: [Xmonad] An intro to installing and configuring xmonad Message-ID: <20070602072310.GB2348@cse.unsw.EDU.AU> I've written a shorter into to building, installing and configuring xmonad. Now available: http://xmonad.org/intro.html It also attempts to compare and contrast with the dwm/wmii family of wms, ion and the ratpoison family. If I've made any factual errors, or missed important points, do let me know. -- Don From nahoo82 at gmail.com Sat Jun 2 03:48:55 2007 From: nahoo82 at gmail.com (Ruben Porras) Date: Sat Jun 2 03:44:47 2007 Subject: [Xmonad] xinerama not working In-Reply-To: <20070602034442.GD1293@cse.unsw.EDU.AU> References: <1180737936.25290.4.camel@localhost> <20070602034442.GD1293@cse.unsw.EDU.AU> Message-ID: <1180770535.5631.9.camel@localhost> Am Samstag, den 02.06.2007, 13:44 +1000 schrieb Donald Bruce Stewart: > nahoo82: > > Hi, > > > > I'm having problems with the xinerama support. I follow the installation > > steps and I run autoreconfigure. The xmonad binary is also linked with > > libXinerama.so. > > Can you check that X11-extras found and built with Xinerama support? > Perhaps provide the configure logs for X11-extras. I think so, this are the steps that I'm following $ runhaskell Setup.lhs configure ... checking X11/extensions/Xinerama.h usability... yes checking X11/extensions/Xinerama.h presence... yes checking for X11/extensions/Xinerama.h... yes configure: creating ./config.status config.status: creating X11-extras.buildinfo config.status: creating include/config.h config.status: include/config.h is unchanged $ runhaskell Setup.lhs build Preprocessing library X11-extras-0.2... Building X11-extras-0.2... /usr/bin/ar: creating dist/build/libHSX11-extras-0.2.a As a test: $ nm dist/build/libHSX11-extras-0.2.a | grep xinerama 000000a0 D X11zmextraszm0zi2_GraphicsziX11ziXinerama_xineramaIsActive_closure 00000c58 T X11zmextraszm0zi2_GraphicsziX11ziXinerama_xineramaIsActive_info 0000009c D X11zmextraszm0zi2_GraphicsziX11ziXinerama_xineramaQueryExtension_closure 00000c40 T X11zmextraszm0zi2_GraphicsziX11ziXinerama_xineramaQueryExtension_info 00000094 D X11zmextraszm0zi2_GraphicsziX11ziXinerama_xineramaQueryScreens_closure 00000c10 T X11zmextraszm0zi2_GraphicsziX11ziXinerama_xineramaQueryScreens_info 00000098 D X11zmextraszm0zi2_GraphicsziX11ziXinerama_xineramaQueryVersion_closure 00000c28 T X11zmextraszm0zi2_GraphicsziX11ziXinerama_xineramaQueryVersion_info $ runhaskell Setup.lhs install --user Installing: /usr/local/lib/X11-extras-0.2/ghc-6.6.1 & /usr/local/bin X11-extras-0.2... Registering X11-extras-0.2... Reading package info from ".installed-pkg-config" ... done. Saving old package config file... done. Writing new package config file... done. Attached is also the buildlog from xmonad. If it helps, I'm usisg xorg 1.3.0 and I'm activating the second monitor through the command xrandr --output VGA --left-of LVDS Thanks -------------- next part -------------- $ runhaskell Setup.lhs configure Configuring xmonad-0.2... configure: Dependency base>=1.0: using base-2.1.1 configure: Dependency X11>=1.2.1: using X11-1.2.1 configure: Dependency X11-extras>=0.2: using X11-extras-0.2 configure: Dependency mtl>=1.0: using mtl-1.0.1 configure: Dependency unix>=1.0: using unix-2.1 configure: Using install prefix: /usr/local configure: Binaries installed in: /usr/local/bin configure: Libraries installed in: /usr/local/lib/xmonad-0.2/ghc-6.6.1 configure: Private binaries installed in: /usr/local/libexec configure: Data files installed in: /usr/local/share/xmonad-0.2 configure: Using compiler: /usr/bin/ghc configure: Compiler flavor: GHC configure: Compiler version: 6.6.1 configure: Using package tool: /usr/bin/ghc-pkg configure: Using ar found on system at: /usr/bin/ar configure: No haddock found configure: No pfesetup found configure: Using ranlib found on system at: /usr/bin/ranlib configure: Using runghc found on system at: /usr/bin/runghc configure: Using runhugs found on system at: /usr/bin/runhugs configure: No happy found configure: No alex found configure: Using hsc2hs: /usr/bin/hsc2hs configure: No c2hs found configure: No cpphs found configure: No greencard found $ runhaskell Setup.lhs build Preprocessing executables for xmonad-0.2... Building xmonad-0.2... [1 of 6] Compiling StackSet ( StackSet.hs, dist/build/xmonad/xmonad-tmp/StackSet.o ) StackSet.hs:270:31: Warning: Pattern match(es) are non-exhaustive In a case alternative: Patterns not matched: Empty StackSet.hs:275:33: Warning: Pattern match(es) are non-exhaustive In a case alternative: Patterns not matched: Empty StackSet.hs:280:30: Warning: Pattern match(es) are non-exhaustive In a case alternative: Patterns not matched: Empty StackSet.hs:285:32: Warning: Pattern match(es) are non-exhaustive In a case alternative: Patterns not matched: Empty StackSet.hs:368:11: Warning: Pattern match(es) are non-exhaustive In a case alternative: Patterns not matched: Empty StackSet.hs:390:34: Warning: Pattern match(es) are non-exhaustive In a case alternative: Patterns not matched: Empty [2 of 6] Compiling XMonad ( XMonad.hs, dist/build/xmonad/xmonad-tmp/XMonad.o ) [3 of 6] Compiling Config[boot] ( Config.hs-boot, nothing ) [4 of 6] Compiling Operations ( Operations.hs, dist/build/xmonad/xmonad-tmp/Operations.o ) [5 of 6] Compiling Config ( Config.hs, dist/build/xmonad/xmonad-tmp/Config.o ) [6 of 6] Compiling Main ( Main.hs, dist/build/xmonad/xmonad-tmp/Main.o ) Linking dist/build/xmonad/xmonad ... $ runhaskell Setup.lhs install Installing: /usr/local/lib/xmonad-0.2/ghc-6.6.1 & /usr/local/bin xmonad-0.2... From sjanssen at cse.unl.edu Sat Jun 2 04:08:58 2007 From: sjanssen at cse.unl.edu (Spencer Janssen) Date: Sat Jun 2 04:04:53 2007 Subject: [Xmonad] xinerama not working In-Reply-To: <1180770535.5631.9.camel@localhost> References: <1180737936.25290.4.camel@localhost> <20070602034442.GD1293@cse.unsw.EDU.AU> <1180770535.5631.9.camel@localhost> Message-ID: <20070602030858.14566eca@localhost> On Sat, 02 Jun 2007 09:48:55 +0200 Ruben Porras wrote: > If it helps, I'm usisg xorg 1.3.0 and I'm activating the second > monitor through the command > > xrandr --output VGA --left-of LVDS Hmm, this should work (I run the same command every day). Are you running xrandr before or after xmonad starts? Does xmonad pick up the right screen geometry after restart (mod-q, make sure xmonad is in your path)? Has your server loaded the Xinerama extension? Check with 'xdpyinfo | grep XINERAMA'. Cheers, Spencer Janssen PS - you should try running Jason's little diagnostic script from an earlier post in this thread From daniel at wagner-home.com Sat Jun 2 04:12:15 2007 From: daniel at wagner-home.com (daniel@wagner-home.com) Date: Sat Jun 2 04:53:20 2007 Subject: [Xmonad] darcs patch: XMonadContrib.ReadMap: a Read instance of Map for GHC ... Message-ID: Fri Jun 1 23:43:18 PDT 2007 daniel@wagner-home.com * XMonadContrib.ReadMap: a Read instance of Map for GHC 6.4 users -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/x-darcs-patch Size: 7066 bytes Desc: A darcs patch for your repository! Url : http://www.haskell.org/pipermail/xmonad/attachments/20070602/d5a42257/attachment-0001.bin From dons at cse.unsw.edu.au Sat Jun 2 05:00:42 2007 From: dons at cse.unsw.edu.au (Donald Bruce Stewart) Date: Sat Jun 2 04:56:22 2007 Subject: [Xmonad] darcs patch: XMonadContrib.ReadMap: a Read instance of Map for GHC ... In-Reply-To: References: Message-ID: <20070602090042.GC2348@cse.unsw.EDU.AU> daniel: > Fri Jun 1 23:43:18 PDT 2007 daniel@wagner-home.com > * XMonadContrib.ReadMap: a Read instance of Map for GHC 6.4 users Applied. Good thinking. -- Don From nahoo82 at gmail.com Sat Jun 2 05:39:24 2007 From: nahoo82 at gmail.com (Ruben Porras) Date: Sat Jun 2 05:35:08 2007 Subject: [Xmonad] xinerama not working In-Reply-To: <20070602030858.14566eca@localhost> References: <1180737936.25290.4.camel@localhost> <20070602034442.GD1293@cse.unsw.EDU.AU> <1180770535.5631.9.camel@localhost> <20070602030858.14566eca@localhost> Message-ID: <1180777164.5033.5.camel@localhost> Am Samstag, den 02.06.2007, 03:08 -0500 schrieb Spencer Janssen: > On Sat, 02 Jun 2007 09:48:55 +0200 > Ruben Porras wrote: > > > If it helps, I'm usisg xorg 1.3.0 and I'm activating the second > > monitor through the command > > > > xrandr --output VGA --left-of LVDS > > Hmm, this should work (I run the same command every day). Are you > running xrandr before or after xmonad starts? after xrandr. Im using the same .xsession file as for ion3, I'm only changing the last line, from exec ion3 to exec xmonad. > Does xmonad pick up the right screen geometry after restart (mod-q, > make sure xmonad is in your path)? the same problem persist, also after closing all the windows and openining a new xterm. Xmonad is in the path. > Has your server loaded the Xinerama extension? Check with 'xdpyinfo | > grep XINERAMA'. yes, it works well with ion3 + the xinerama module and with metacity. > PS - you should try running Jason's little diagnostic script from an > earlier post in this thread I cannot find the script in the archives, could someone mail it to me? Thanks. From dons at cse.unsw.edu.au Sat Jun 2 05:55:06 2007 From: dons at cse.unsw.edu.au (Donald Bruce Stewart) Date: Sat Jun 2 05:50:44 2007 Subject: [Xmonad] xinerama not working In-Reply-To: <1180777164.5033.5.camel@localhost> References: <1180737936.25290.4.camel@localhost> <20070602034442.GD1293@cse.unsw.EDU.AU> <1180770535.5631.9.camel@localhost> <20070602030858.14566eca@localhost> <1180777164.5033.5.camel@localhost> Message-ID: <20070602095506.GD2348@cse.unsw.EDU.AU> nahoo82: > Am Samstag, den 02.06.2007, 03:08 -0500 schrieb Spencer Janssen: > > On Sat, 02 Jun 2007 09:48:55 +0200 > > Ruben Porras wrote: > > > > > If it helps, I'm usisg xorg 1.3.0 and I'm activating the second > > > monitor through the command > > > > > > xrandr --output VGA --left-of LVDS > > > > Hmm, this should work (I run the same command every day). Are you > > running xrandr before or after xmonad starts? > > after xrandr. Im using the same .xsession file as for ion3, I'm only > changing the last line, from exec ion3 to exec xmonad. > > > Does xmonad pick up the right screen geometry after restart (mod-q, > > make sure xmonad is in your path)? > > the same problem persist, also after closing all the windows and > openining a new xterm. Xmonad is in the path. > > > Has your server loaded the Xinerama extension? Check with 'xdpyinfo | > > grep XINERAMA'. > > yes, it works well with ion3 + the xinerama module and with metacity. > > > PS - you should try running Jason's little diagnostic script from an > > earlier post in this thread > > I cannot find the script in the archives, could someone mail it to me? Here's the script, http://www.haskell.org/pipermail/xmonad/2007-June/000494.html -- Don From chris at cmears.id.au Sat Jun 2 07:44:09 2007 From: chris at cmears.id.au (Chris Mears) Date: Sat Jun 2 07:41:25 2007 Subject: [Xmonad] darcs patch: Fix out-of-date comment in Config.hs. Message-ID: Sat Jun 2 21:43:12 EST 2007 Chris Mears * Fix out-of-date comment in Config.hs. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/x-darcs-patch Size: 2099 bytes Desc: A darcs patch for your repository! Url : http://www.haskell.org/pipermail/xmonad/attachments/20070602/786f81ce/attachment.bin From nahoo82 at gmail.com Sat Jun 2 07:52:09 2007 From: nahoo82 at gmail.com (Ruben Porras) Date: Sat Jun 2 07:47:52 2007 Subject: [Xmonad] xinerama not working In-Reply-To: <20070602030858.14566eca@localhost> References: <1180737936.25290.4.camel@localhost> <20070602034442.GD1293@cse.unsw.EDU.AU> <1180770535.5631.9.camel@localhost> <20070602030858.14566eca@localhost> Message-ID: <1180785129.5033.9.camel@localhost> Am Samstag, den 02.06.2007, 03:08 -0500 schrieb Spencer Janssen: > On Sat, 02 Jun 2007 09:48:55 +0200 > Ruben Porras wrote: > PS - you should try running Jason's little diagnostic script from an > earlier post in this thread The output is: Nothing [Rectangle {rect_x = 0, rect_y = 0, rect_width = 2304, rect_height = 1024}] the version of x11-extras and xmonad, are the darcs from yesterday. From glasser at mit.edu Sat Jun 2 10:13:36 2007 From: glasser at mit.edu (David Glasser) Date: Sat Jun 2 10:09:12 2007 Subject: [Xmonad] darcs patch: first shot at a floating layer In-Reply-To: <4661030F.3050101@stanford.edu> References: <20070531053230.GH25344@cse.unsw.EDU.AU> <20070531062218.GJ25344@cse.unsw.EDU.AU> <876468rapd.fsf@cenderis.demon.co.uk> <20070601025130.GG31292@cse.unsw.EDU.AU> <1ea387f60705312022v291821cdu79a32bfa8f13f526@mail.gmail.com> <4661030F.3050101@stanford.edu> Message-ID: <1ea387f60706020713i4f5b7d57ga584f2b2341bd0a4@mail.gmail.com> On 6/2/07, Daniel Wagner wrote: > David Glasser wrote: > > Excellent. The only downside to doing it this way is that to have > > different bars on different windows, you'd have to make the output > > You shouldn't need to do any fancy multiplexing, or have different > status bars on different workspaces. Just send a new line (that has the > updated workspace number) to dzen's stdin. Ah, but I *want* to have one status bar per (Xinerama) screen. --dave -- David Glasser | glasser@mit.edu | http://www.davidglasser.net/ From sjanssen at cse.unl.edu Sat Jun 2 14:00:40 2007 From: sjanssen at cse.unl.edu (Spencer Janssen) Date: Sat Jun 2 13:56:27 2007 Subject: [Xmonad] darcs patch: Fix out-of-date comment in Config.hs. In-Reply-To: References: Message-ID: <20070602130040.54aa5657@localhost> On Sat, 02 Jun 2007 21:44:09 +1000 Chris Mears wrote: > Sat Jun 2 21:43:12 EST 2007 Chris Mears > * Fix out-of-date comment in Config.hs. Applied, thanks. From jcreigh at gmail.com Sat Jun 2 14:01:34 2007 From: jcreigh at gmail.com (Jason Creighton) Date: Sat Jun 2 13:57:12 2007 Subject: [Xmonad] Howtos wanted: Configuring xmonad with display managers Message-ID: <20070602180134.GA5064@jpc.example.com> 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 From xmonad at cenderis.demon.co.uk Sat Jun 2 14:38:45 2007 From: xmonad at cenderis.demon.co.uk (Bruce Stephens) Date: Sat Jun 2 14:34:21 2007 Subject: [Xmonad] Howtos wanted: Configuring xmonad with display managers In-Reply-To: <20070602180134.GA5064@jpc.example.com> (Jason Creighton's message of "Sat\, 2 Jun 2007 12\:01\:34 -0600") References: <20070602180134.GA5064@jpc.example.com> Message-ID: <87zm3imcay.fsf@cenderis.demon.co.uk> Jason Creighton writes: [...] > 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. I'm running Debian unstable with gdm, and I just have an executable script ~/.xsession which (after running ssh-agent, etc.) runs xmonad. As, before, it ran ion3. The rule is that once ~/.xsession exits the session ends. So normally the window manager is the last thing you run, and it's not run in the background. From xmonad at cenderis.demon.co.uk Sat Jun 2 14:57:38 2007 From: xmonad at cenderis.demon.co.uk (Bruce Stephens) Date: Sat Jun 2 14:53:13 2007 Subject: [Xmonad] Howtos wanted: Configuring xmonad with display managers In-Reply-To: <87zm3imcay.fsf@cenderis.demon.co.uk> (Bruce Stephens's message of "Sat\, 02 Jun 2007 19\:38\:45 +0100") References: <20070602180134.GA5064@jpc.example.com> <87zm3imcay.fsf@cenderis.demon.co.uk> Message-ID: <87vee6mbfh.fsf@cenderis.demon.co.uk> Bruce Stephens writes: [...] > I'm running Debian unstable with gdm, and I just have an executable > script ~/.xsession which (after running ssh-agent, etc.) runs xmonad. > As, before, it ran ion3. Shows how long ago I first started doing this: the critical step is to choose the Xsession session when logging in to gdm. I imagine kdm does something similar. By default they'll give you a typical gnome or kde setup (modified by local files), but you can ask for the traditional option which mostly involves running ~/.xsession, if it exists, and some default script otherwise. There are (typically) some stumbling blocks to do with PATH and so on, but I imagine most people could resolve those easily enough once they'd at least got the right window manager running. [...] From jeremy at n-heptane.com Sat Jun 2 15:17:06 2007 From: jeremy at n-heptane.com (Jeremy Shaw) Date: Sat Jun 2 15:13:01 2007 Subject: [Xmonad] Howtos wanted: Configuring xmonad with display managers In-Reply-To: <20070602180134.GA5064@jpc.example.com> References: <20070602180134.GA5064@jpc.example.com> Message-ID: At Sat, 2 Jun 2007 12:01:34 -0600, Jason Creighton wrote: > > 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. For kde you can set the environment variable KDEWM=xmonad. Then KDE will start like normal, but it will use xmonad instead of kwin. I believe you would have to make your .xsession look something like this: #!/bin/sh export KDEWM=/usr/local/bin/xmonad /usr/bin/x-session-manager However, I have not tested this. hth, j. From alec at thened.net Sat Jun 2 16:24:49 2007 From: alec at thened.net (Alec Berryman) Date: Sat Jun 2 16:22:21 2007 Subject: [Xmonad] Howtos wanted: Configuring xmonad with display managers In-Reply-To: <20070602180134.GA5064@jpc.example.com> References: <20070602180134.GA5064@jpc.example.com> Message-ID: <20070602202449.GA3840@thened.net> Jason Creighton on 2007-06-02 12:01:34 -0600: > Is anybody running [xgk]dm with xmonad? If so, how? I'm using xdm on Debian testing. Create an ~/.xsession just as you would an ~/.xinitrc (mine are symlinked), making sure the last line is "exec /path/to/xmonad", and you're good to go. From wagnerd at stanford.edu Sat Jun 2 19:22:58 2007 From: wagnerd at stanford.edu (Daniel Wagner) Date: Sat Jun 2 19:18:30 2007 Subject: [Xmonad] Howtos wanted: Configuring xmonad with display managers In-Reply-To: <20070602180134.GA5064@jpc.example.com> References: <20070602180134.GA5064@jpc.example.com> Message-ID: <4661FBD2.10102@stanford.edu> Jason Creighton wrote: > Is anybody running [xgk]dm with xmonad? If so, how? Please post your > answer here, stating what distro you're running (is anybody running Hey, I'm running xmonad under gdm in Ubuntu Dapper. All I had to do was create an extra file; the location varies by distribution, but mine had to go in /usr/share/xsessions: ~% cat /usr/share/xsessions/xmonad.desktop [Desktop Entry] Encoding=UTF-8 Name=xmonad Comment=This session starts xmonad Exec=/usr/local/bin/xmonad Type=Application Then, when logging in, you can select "xmonad" as a session in the "Options" menu in the lower-left hand corner of the login screen. ~d From dons at cse.unsw.edu.au Sat Jun 2 20:49:26 2007 From: dons at cse.unsw.edu.au (Donald Bruce Stewart) Date: Sat Jun 2 20:45:03 2007 Subject: [Xmonad] xinerama not working In-Reply-To: <1180785129.5033.9.camel@localhost> References: <1180737936.25290.4.camel@localhost> <20070602034442.GD1293@cse.unsw.EDU.AU> <1180770535.5631.9.camel@localhost> <20070602030858.14566eca@localhost> <1180785129.5033.9.camel@localhost> Message-ID: <20070603004926.GB2241@cse.unsw.EDU.AU> nahoo82: > Am Samstag, den 02.06.2007, 03:08 -0500 schrieb Spencer Janssen: > > On Sat, 02 Jun 2007 09:48:55 +0200 > > Ruben Porras wrote: > > > PS - you should try running Jason's little diagnostic script from an > > earlier post in this thread > > > The output is: > > Nothing > [Rectangle {rect_x = 0, rect_y = 0, rect_width = 2304, rect_height = > 1024}] > > the version of x11-extras and xmonad, are the darcs from yesterday. > Ok. We're officially mystified. If X11-extras was correctly built with Xinerama, and Xinerama is enabled on your system, the above should have found a couple of screens -- its a simple call into X after all. Any further information about your system that might be relevant? -- Don From codesite-noreply at google.com Sat Jun 2 21:35:54 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Sat Jun 2 21:31:28 2007 Subject: [Xmonad] Issue 12 in project xmonad Message-ID: Issue 12: Support _NET_WM_STRUT property for status bar programs http://code.google.com/p/xmonad/issues/detail?id=12 Comment #1 by dons00: Automated support for docks, gkrellm et al, should be in 0.3. Its a too FAQ. Issue attribute updates: 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 From codesite-noreply at google.com Sat Jun 2 21:37:27 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Sat Jun 2 21:33:00 2007 Subject: [Xmonad] Issue 18 in project xmonad Message-ID: Issue 18: Support other task bar / dock properties? http://code.google.com/p/xmonad/issues/detail?id=18 Comment #2 by dons00: A solution needed for 0.3. Issue attribute updates: 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 From codesite-noreply at google.com Sat Jun 2 21:42:51 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Sat Jun 2 21:38:25 2007 Subject: [Xmonad] Issue 4 in project xmonad Message-ID: <163600d6850431f691084f4b59fd6@google.com> Issue 4: Implement float layer http://code.google.com/p/xmonad/issues/detail?id=4 Comment #3 by dons00: The floating layer as is needs to have a couple of issues addressed before 0.3: * interaction with the underlying tiled layer is awkward * needs well defined semantics for moving between tiled and floating windows * large floating windows in fullscreen mode can be confusing -- 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 From stepan at golosunov.pp.ru Sun Jun 3 02:44:09 2007 From: stepan at golosunov.pp.ru (Stepan Golosunov) Date: Sun Jun 3 02:45:24 2007 Subject: [Xmonad] Howtos wanted: Configuring xmonad with display managers In-Reply-To: <20070602180134.GA5064@jpc.example.com> References: <20070602180134.GA5064@jpc.example.com> Message-ID: <20070603064408.GA9912@sghpc.golosunov.pp.ru> 02.06.2007 ? 12:01:34 -0600 Jason Creighton ???????: > 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. I am running xmonad on Debian with xdm from ~/.xsession which contains: #!/bin/zsh if [ -d ~/bin ]; then PATH=~/bin:"${PATH}" export PATH fi xmodmap -e 'add mod4 = Super_L' -e 'add mod4 = Super_R' (xscreensaver&) (emacs&) (urxvt&) exec xmonad Also, xmonad does not properly handle its children exiting, so I have to start programs as "(urxvt&)" instead of "urxvt&" to prevent them from becoming zombies (or I could just remove "exec"). From dons at cse.unsw.edu.au Sun Jun 3 03:01:11 2007 From: dons at cse.unsw.edu.au (Donald Bruce Stewart) Date: Sun Jun 3 02:56:47 2007 Subject: [Xmonad] Howtos wanted: Configuring xmonad with display managers In-Reply-To: <20070603064408.GA9912@sghpc.golosunov.pp.ru> References: <20070602180134.GA5064@jpc.example.com> <20070603064408.GA9912@sghpc.golosunov.pp.ru> Message-ID: <20070603070111.GE2241@cse.unsw.EDU.AU> stepan: > 02.06.2007 ? 12:01:34 -0600 Jason Creighton ???????: > > 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. > > I am running xmonad on Debian with xdm from ~/.xsession which contains: > > #!/bin/zsh > if [ -d ~/bin ]; then > PATH=~/bin:"${PATH}" > export PATH > fi > xmodmap -e 'add mod4 = Super_L' -e 'add mod4 = Super_R' > (xscreensaver&) > (emacs&) > (urxvt&) > exec xmonad > > Also, xmonad does not properly handle its children exiting, so I have > to start programs as "(urxvt&)" instead of "urxvt&" to prevent them > from becoming zombies (or I could just remove "exec"). Oh hmm. That sounds like a bug report. -- Don From codesite-noreply at google.com Sun Jun 3 03:54:22 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Sun Jun 3 03:49:55 2007 Subject: [Xmonad] Issue 20 in project xmonad Message-ID: <163600cefd0431fbc1a63c0d6a0b9@google.com> Issue 20: xrandr to make the resolution lesser does not update the geometry http://code.google.com/p/xmonad/issues/detail?id=20 Comment #3 by SpencerJanssen: In the non-Xinerama path, getScreenInfo uses Xlib's DisplayWidth/Height. Xlib (dubiously) caches these values. Instead of trusting Xlib, we check the dimensions of the root window. 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 From dons at cse.unsw.edu.au Sun Jun 3 06:58:51 2007 From: dons at cse.unsw.edu.au (Donald Bruce Stewart) Date: Sun Jun 3 06:54:27 2007 Subject: [Xmonad] xinerama not working Message-ID: <20070603105851.GA5205@cse.unsw.EDU.AU> ----- Forwarded message from Ruben Porras ----- Date: Sun, 03 Jun 2007 12:42:59 +0200 From: Ruben Porras To: Donald Bruce Stewart Subject: Re: [Xmonad] xinerama not working Am Sonntag, den 03.06.2007, 10:49 +1000 schrieb Donald Bruce Stewart: > Ok. We're officially mystified. If X11-extras was correctly built with > Xinerama, and Xinerama is enabled on your system, the above should have > found a couple of screens -- its a simple call into X after all. After updating today to the darcs x11-extras version everything works like a charm. Thanks ----- End forwarded message ----- From codesite-noreply at google.com Sun Jun 3 07:50:31 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Sun Jun 3 07:46:03 2007 Subject: [Xmonad] Issue 16 in project xmonad Message-ID: <163600d6850431ff0e2df8cc71a28@google.com> Issue 16: xmonad does not mark non-visible windows as iconafied http://code.google.com/p/xmonad/issues/detail?id=16 Comment #2 by dons00: Setting WMState to IconicState seems the right thing to do here. Issue attribute updates: Status: Started 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 From xmonad at cenderis.demon.co.uk Sun Jun 3 08:06:30 2007 From: xmonad at cenderis.demon.co.uk (Bruce Stephens) Date: Sun Jun 3 08:02:04 2007 Subject: [Xmonad] xinerama not working In-Reply-To: <20070603004926.GB2241@cse.unsw.EDU.AU> (Donald Bruce Stewart's message of "Sun\, 3 Jun 2007 10\:49\:26 +1000") References: <1180737936.25290.4.camel@localhost> <20070602034442.GD1293@cse.unsw.EDU.AU> <1180770535.5631.9.camel@localhost> <20070602030858.14566eca@localhost> <1180785129.5033.9.camel@localhost> <20070603004926.GB2241@cse.unsw.EDU.AU> Message-ID: <87bqfxnsxl.fsf@cenderis.demon.co.uk> dons@cse.unsw.edu.au (Donald Bruce Stewart) writes: [...] > Ok. We're officially mystified. If X11-extras was correctly built with > Xinerama, and Xinerama is enabled on your system, the above should have > found a couple of screens -- its a simple call into X after all. It's probably worth looking at what's actually in Graphics/X11 in the source for X11-extras. I managed somehow to get to the situation where everything was linked to libXinerama, but it was still using the dummy functions that didn't use it. (Though the nm output you gave also looks plausible, so probably this isn't it.) [...] From joelkoerwer at gmail.com Sun Jun 3 10:03:28 2007 From: joelkoerwer at gmail.com (Joel Koerwer) Date: Sun Jun 3 09:59:01 2007 Subject: [Xmonad] Howtos wanted: Configuring xmonad with display managers In-Reply-To: <20070602180134.GA5064@jpc.example.com> References: <20070602180134.GA5064@jpc.example.com> Message-ID: <34e5cfb80706030703u86135eegaffbdf6cc5fe907f@mail.gmail.com> I'm using gdm. I created a /usr/share/xsessions/xmonad.desktop by modifying gnome.desktop from the same directory. I basically just changed the name and executable but didn't bother with all the localization names. Then you can choose xmonad from the login screen. The .xsession method is of course simpler for a local install... such as mine. Oh well. -- Joel From rob.manea at googlemail.com Sun Jun 3 15:21:27 2007 From: rob.manea at googlemail.com (Robert Manea) Date: Sun Jun 3 15:17:03 2007 Subject: [Xmonad] [dzen] release 0.3.5 Message-ID: <20070603192127.GA20807@deski.rob-home.homeip.net> Hello, this release * fixed a bug in multiline handling * added an optional timeout argument to "-p" (thanks Adam Langley) * added a new scrollhome action * improved scrolldown/scrollup actions to take the number of lines to scroll as option * cleaned up config.mk (thanks David Glasser) Get it here: http://gotmor.googlepages.com/dzen Bye, Rob. P.S.: If you are using dzen for any interesting task and would like to share your script be sure to send me a mail with a short description and the script in order to populate dzen's script archive (http://gotmor.googlepages.com/dzenscriptarchive). From stefanor at cox.net Sun Jun 3 16:37:20 2007 From: stefanor at cox.net (Stefan O'Rear) Date: Sun Jun 3 16:32:54 2007 Subject: [Xmonad] darcs patch: Add poker for ConfigureEvent Message-ID: Sun Jun 3 11:50:16 PDT 2007 Stefan O'Rear * Add poker for ConfigureEvent -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/x-darcs-patch Size: 1047 bytes Desc: A darcs patch for your repository! Url : http://www.haskell.org/pipermail/xmonad/attachments/20070603/56a44ae0/attachment.bin From stefanor at cox.net Sun Jun 3 16:38:29 2007 From: stefanor at cox.net (Stefan O'Rear) Date: Sun Jun 3 16:34:03 2007 Subject: [Xmonad] darcs patch: Correctly handle resize requests (-12 +22) Message-ID: Sun Jun 3 13:31:53 PDT 2007 Stefan O'Rear * Correctly handle resize requests (-12 +22) Xmonad now implements resize requests in a consistent manner. * If the window is FLOATING, we implement the program's request, and correctly update the StackSet; so it will keep the new size. This should work correctly even for non-current windows. * Otherwise, we ignore the request. As per ICCCM, we send a fake ConfigureNotify containing the new (unchanged) geometry. This is perfectly ICCCM compliant, and if it breaks your client, it's your own fault. This patch requires setConfigureEvent, which is added to X11-extras by a patch approximately contemporaneous with this one. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/x-darcs-patch Size: 4401 bytes Desc: A darcs patch for your repository! Url : http://www.haskell.org/pipermail/xmonad/attachments/20070603/7af8debb/attachment.bin From sjanssen at cse.unl.edu Sun Jun 3 17:02:55 2007 From: sjanssen at cse.unl.edu (Spencer Janssen) Date: Sun Jun 3 16:58:35 2007 Subject: [Xmonad] darcs patch: Add poker for ConfigureEvent In-Reply-To: References: Message-ID: <20070603160255.705a3297@localhost> On Sun, 03 Jun 2007 13:37:20 -0700 "Stefan O'Rear" wrote: > Sun Jun 3 11:50:16 PDT 2007 Stefan O'Rear > * Add poker for ConfigureEvent Applied, thanks. From sjanssen at cse.unl.edu Sun Jun 3 17:25:00 2007 From: sjanssen at cse.unl.edu (Spencer Janssen) Date: Sun Jun 3 17:20:38 2007 Subject: [Xmonad] darcs patch: Correctly handle resize requests (-12 +22) In-Reply-To: References: Message-ID: <20070603162500.5176ed6e@localhost> On Sun, 03 Jun 2007 13:38:29 -0700 "Stefan O'Rear" wrote: > Sun Jun 3 13:31:53 PDT 2007 Stefan O'Rear > * Correctly handle resize requests (-12 +22) > Xmonad now implements resize requests in a consistent manner. > > * If the window is FLOATING, we implement the program's request, and > correctly update the StackSet; so it will keep the new size. This > should work correctly even for non-current windows. > > * Otherwise, we ignore the request. As per ICCCM, we send a fake > ConfigureNotify containing the new (unchanged) geometry. This is > perfectly ICCCM compliant, and if it breaks your client, it's your > own fault. > > This patch requires setConfigureEvent, which is added to X11-extras > by a patch approximately contemporaneous with this one. Applied, thanks. From jcreigh at gmail.com Sun Jun 3 17:32:01 2007 From: jcreigh at gmail.com (Jason Creighton) Date: Sun Jun 3 17:27:37 2007 Subject: [Xmonad] xinerama not working In-Reply-To: <87bqfxnsxl.fsf@cenderis.demon.co.uk> References: <1180737936.25290.4.camel@localhost> <20070602034442.GD1293@cse.unsw.EDU.AU> <1180770535.5631.9.camel@localhost> <20070602030858.14566eca@localhost> <1180785129.5033.9.camel@localhost> <20070603004926.GB2241@cse.unsw.EDU.AU> <87bqfxnsxl.fsf@cenderis.demon.co.uk> Message-ID: <20070603213201.GA583@jpc.example.com> On Sun, Jun 03, 2007 at 01:06:30PM +0100, Bruce Stephens wrote: > dons@cse.unsw.edu.au (Donald Bruce Stewart) writes: > > [...] > > > Ok. We're officially mystified. If X11-extras was correctly built with > > Xinerama, and Xinerama is enabled on your system, the above should have > > found a couple of screens -- its a simple call into X after all. > > It's probably worth looking at what's actually in Graphics/X11 in the > source for X11-extras. I managed somehow to get to the situation > where everything was linked to libXinerama, but it was still using the > dummy functions that didn't use it. (Though the nm output you gave > also looks plausible, so probably this isn't it.) If you managed to do that, it's definitely a bug. Are you able to reproduce this behavior? Jason Creighton From xmonad at cenderis.demon.co.uk Sun Jun 3 17:54:50 2007 From: xmonad at cenderis.demon.co.uk (Bruce Stephens) Date: Sun Jun 3 17:50:22 2007 Subject: [Xmonad] xinerama not working In-Reply-To: <20070603213201.GA583@jpc.example.com> (Jason Creighton's message of "Sun\, 3 Jun 2007 15\:32\:01 -0600") References: <1180737936.25290.4.camel@localhost> <20070602034442.GD1293@cse.unsw.EDU.AU> <1180770535.5631.9.camel@localhost> <20070602030858.14566eca@localhost> <1180785129.5033.9.camel@localhost> <20070603004926.GB2241@cse.unsw.EDU.AU> <87bqfxnsxl.fsf@cenderis.demon.co.uk> <20070603213201.GA583@jpc.example.com> Message-ID: <87zm3g1z6d.fsf@cenderis.demon.co.uk> Jason Creighton writes: > On Sun, Jun 03, 2007 at 01:06:30PM +0100, Bruce Stephens wrote: [...] >> It's probably worth looking at what's actually in Graphics/X11 in the >> source for X11-extras. I managed somehow to get to the situation >> where everything was linked to libXinerama, but it was still using the >> dummy functions that didn't use it. (Though the nm output you gave >> also looks plausible, so probably this isn't it.) > > If you managed to do that, it's definitely a bug. Are you able to > reproduce this behavior? Almost certainly not. It was quite possibly user error: I was messing about quite a bit, trying to work out what was wrong. My guess is it won't happen to anyone following the instructions properly (in particular, running autoconf), or just using more recent tarballs or darcs downloads. From xmonad at cenderis.demon.co.uk Sun Jun 3 19:03:38 2007 From: xmonad at cenderis.demon.co.uk (Bruce Stephens) Date: Sun Jun 3 18:59:10 2007 Subject: [Xmonad] darcs patch: Correctly handle resize requests (-12 +22) In-Reply-To: (Stefan O'Rear's message of "Sun\, 03 Jun 2007 13\:38\:29 -0700") References: Message-ID: <878xb0d4j9.fsf@cenderis.demon.co.uk> Stefan O'Rear writes: > Sun Jun 3 13:31:53 PDT 2007 Stefan O'Rear > * Correctly handle resize requests (-12 +22) > Xmonad now implements resize requests in a consistent manner. > > * If the window is FLOATING, we implement the program's request, and > correctly update the StackSet; so it will keep the new size. This > should work correctly even for non-current windows. > > * Otherwise, we ignore the request. As per ICCCM, we send a fake > ConfigureNotify containing the new (unchanged) geometry. This is > perfectly ICCCM compliant, and if it breaks your client, it's your > own fault. > > This patch requires setConfigureEvent, which is added to X11-extras by > a patch approximately contemporaneous with this one. This doesn't seem to work quite right (for me, anyway). I find that all transient windows now appear at (0,0). (I've not noticed the resizing behaviour, particularly, so that may well have been improved.) [...] From sjanssen at cse.unl.edu Sun Jun 3 19:50:41 2007 From: sjanssen at cse.unl.edu (Spencer Janssen) Date: Sun Jun 3 19:46:28 2007 Subject: [Xmonad] darcs patch: Correctly handle resize requests (-12 +22) In-Reply-To: <878xb0d4j9.fsf@cenderis.demon.co.uk> References: <878xb0d4j9.fsf@cenderis.demon.co.uk> Message-ID: <20070603185041.204b934d@localhost> On Mon, 04 Jun 2007 00:03:38 +0100 Bruce Stephens wrote: > This doesn't seem to work quite right (for me, anyway). I find that > all transient windows now appear at (0,0). (I've not noticed the > resizing behaviour, particularly, so that may well have been > improved.) Just pushed a fix, is the problem resolved now? Cheers, Spencer Janssen From xmonad at cenderis.demon.co.uk Sun Jun 3 19:58:12 2007 From: xmonad at cenderis.demon.co.uk (Bruce Stephens) Date: Sun Jun 3 19:53:44 2007 Subject: [Xmonad] border colours Message-ID: <874plod20b.fsf@cenderis.demon.co.uk> 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? From xmonad at cenderis.demon.co.uk Sun Jun 3 20:04:35 2007 From: xmonad at cenderis.demon.co.uk (Bruce Stephens) Date: Sun Jun 3 20:00:06 2007 Subject: [Xmonad] darcs patch: Correctly handle resize requests (-12 +22) In-Reply-To: <20070603185041.204b934d@localhost> (Spencer Janssen's message of "Sun\, 3 Jun 2007 18\:50\:41 -0500") References: <878xb0d4j9.fsf@cenderis.demon.co.uk> <20070603185041.204b934d@localhost> Message-ID: <87zm3gbn58.fsf@cenderis.demon.co.uk> Spencer Janssen writes: > On Mon, 04 Jun 2007 00:03:38 +0100 > Bruce Stephens wrote: > >> This doesn't seem to work quite right (for me, anyway). I find that >> all transient windows now appear at (0,0). (I've not noticed the >> resizing behaviour, particularly, so that may well have been >> improved.) > > Just pushed a fix, is the problem resolved now? Yes, that fixed it. From codesite-noreply at google.com Sun Jun 3 20:29:53 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Sun Jun 3 20:25:24 2007 Subject: [Xmonad] Issue 16 in project xmonad Message-ID: Issue 16: xmonad does not mark non-visible windows as iconafied http://code.google.com/p/xmonad/issues/detail?id=16 Comment #3 by dons00: I note that correctly handling WMState, and conforming to the spec, will let xkill work -- 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 From dons at cse.unsw.edu.au Sun Jun 3 21:18:03 2007 From: dons at cse.unsw.edu.au (Donald Bruce Stewart) Date: Sun Jun 3 21:13:37 2007 Subject: [Xmonad] border colours In-Reply-To: <874plod20b.fsf@cenderis.demon.co.uk> References: <874plod20b.fsf@cenderis.demon.co.uk> Message-ID: <20070604011803.GA3113@cse.unsw.EDU.AU> xmonad: > 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? I think this is an interesting issue. Magenta seems a bit horrible though :-) Perhaps we can just suggest some higher visibility settings on the web page? -- Don From stefanor at cox.net Sun Jun 3 21:40:13 2007 From: stefanor at cox.net (Stefan O'Rear) Date: Sun Jun 3 21:35:47 2007 Subject: [Xmonad] darcs patch: do not cache atom values within Xmonad, instead let Xl... Message-ID: Sun Jun 3 18:39:38 PDT 2007 Stefan O'Rear * do not cache atom values within Xmonad, instead let Xlib worry about caching (a documented feature) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/x-darcs-patch Size: 3903 bytes Desc: A darcs patch for your repository! Url : http://www.haskell.org/pipermail/xmonad/attachments/20070603/8bb3ec6b/attachment.bin From sjanssen at cse.unl.edu Sun Jun 3 21:45:41 2007 From: sjanssen at cse.unl.edu (Spencer Janssen) Date: Sun Jun 3 21:41:19 2007 Subject: [Xmonad] darcs patch: do not cache atom values within Xmonad, instead let Xl... In-Reply-To: References: Message-ID: <20070603204541.38d81677@localhost> On Sun, 03 Jun 2007 18:40:13 -0700 "Stefan O'Rear" wrote: > Sun Jun 3 18:39:38 PDT 2007 Stefan O'Rear > * do not cache atom values within Xmonad, instead let Xlib worry > about caching (a documented feature) Applied, thanks. From stefanor at cox.net Sun Jun 3 22:51:13 2007 From: stefanor at cox.net (Stefan O'Rear) Date: Sun Jun 3 22:46:48 2007 Subject: [Xmonad] darcs patch: Add changeProperty16 and changeProperty32 Message-ID: Sun Jun 3 19:49:58 PDT 2007 Stefan O'Rear * Add changeProperty16 and changeProperty32 Also fixes an API bug in changeProperty8 (Char /= 8 bits) that I'm pretty sure nobody depends on. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/x-darcs-patch Size: 1500 bytes Desc: A darcs patch for your repository! Url : http://www.haskell.org/pipermail/xmonad/attachments/20070603/a420f26a/attachment.bin From sjanssen at cse.unl.edu Sun Jun 3 23:10:27 2007 From: sjanssen at cse.unl.edu (Spencer Janssen) Date: Sun Jun 3 23:06:05 2007 Subject: [Xmonad] darcs patch: Add changeProperty16 and changeProperty32 In-Reply-To: References: Message-ID: <20070603221027.20bc9fb7@localhost> On Sun, 03 Jun 2007 19:51:13 -0700 "Stefan O'Rear" wrote: > Sun Jun 3 19:49:58 PDT 2007 Stefan O'Rear > * Add changeProperty16 and changeProperty32 > Also fixes an API bug in changeProperty8 (Char /= 8 bits) that I'm > pretty sure nobody depends on. Applied, thanks. From stefanor at cox.net Mon Jun 4 00:08:13 2007 From: stefanor at cox.net (Stefan O'Rear) Date: Mon Jun 4 00:03:47 2007 Subject: [Xmonad] darcs patch: Add XUnmapWindow binding Message-ID: Sun Jun 3 20:50:56 PDT 2007 Stefan O'Rear * Add XUnmapWindow binding -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/x-darcs-patch Size: 862 bytes Desc: A darcs patch for your repository! Url : http://www.haskell.org/pipermail/xmonad/attachments/20070603/ef075d7f/attachment.bin From sjanssen at cse.unl.edu Mon Jun 4 00:12:06 2007 From: sjanssen at cse.unl.edu (Spencer Janssen) Date: Mon Jun 4 00:07:44 2007 Subject: [Xmonad] darcs patch: Add XUnmapWindow binding In-Reply-To: References: Message-ID: <20070603231206.047c4faa@localhost> On Sun, 03 Jun 2007 21:08:13 -0700 "Stefan O'Rear" wrote: > Sun Jun 3 20:50:56 PDT 2007 Stefan O'Rear > * Add XUnmapWindow binding Applied, thanks. From stefanor at cox.net Mon Jun 4 00:12:35 2007 From: stefanor at cox.net (Stefan O'Rear) Date: Mon Jun 4 00:08:19 2007 Subject: [Xmonad] darcs patch: Set WM_STATE, iconify invisible windows (+9 loc) Message-ID: Sun Jun 3 21:10:29 PDT 2007 Stefan O'Rear * Set WM_STATE, iconify invisible windows (+9 loc) Note that this breaks compatibility with certain programs described as "obsolete" in the ICCCM (1994). See the command above the UnmapEvent handler for details. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/x-darcs-patch Size: 6530 bytes Desc: A darcs patch for your repository! Url : http://www.haskell.org/pipermail/xmonad/attachments/20070603/ed1bfbf8/attachment-0001.bin From stefanor at cox.net Mon Jun 4 00:24:47 2007 From: stefanor at cox.net (Stefan O'Rear) Date: Mon Jun 4 00:20:22 2007 Subject: [Xmonad] darcs patch: Set WM_STATE, iconify invisible windows (+9 loc) Message-ID: Sun Jun 3 21:23:43 PDT 2007 Stefan O'Rear * Set WM_STATE, iconify invisible windows (+9 loc) Note that this breaks compatibility with certain programs described as "obsolete" in the ICCCM (1994). See the command above the UnmapEvent handler for details. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/x-darcs-patch Size: 7011 bytes Desc: A darcs patch for your repository! Url : http://www.haskell.org/pipermail/xmonad/attachments/20070603/b1020e2b/attachment.bin From sjanssen at cse.unl.edu Mon Jun 4 00:25:07 2007 From: sjanssen at cse.unl.edu (Spencer Janssen) Date: Mon Jun 4 00:20:58 2007 Subject: [Xmonad] darcs patch: Set WM_STATE, iconify invisible windows (+9 loc) In-Reply-To: References: Message-ID: <20070603232507.22a73ce6@localhost> On Sun, 03 Jun 2007 21:12:35 -0700 "Stefan O'Rear" wrote: > Sun Jun 3 21:10:29 PDT 2007 Stefan O'Rear > * Set WM_STATE, iconify invisible windows (+9 loc) > Note that this breaks compatibility with certain programs described > as "obsolete" in the ICCCM (1994). See the command above the > UnmapEvent handler for details. Has conflicts, I'll apply the other version of this patch. From sjanssen at cse.unl.edu Mon Jun 4 00:28:50 2007 From: sjanssen at cse.unl.edu (Spencer Janssen) Date: Mon Jun 4 00:24:29 2007 Subject: [Xmonad] darcs patch: Set WM_STATE, iconify invisible windows (+9 loc) In-Reply-To: References: Message-ID: <20070603232850.3f2f14ed@localhost> On Sun, 03 Jun 2007 21:24:47 -0700 "Stefan O'Rear" wrote: > Sun Jun 3 21:23:43 PDT 2007 Stefan O'Rear > * Set WM_STATE, iconify invisible windows (+9 loc) > Note that this breaks compatibility with certain programs described > as "obsolete" in the ICCCM (1994). See the command above the > UnmapEvent handler for details. Applied, thanks. From stefanor at cox.net Mon Jun 4 00:47:42 2007 From: stefanor at cox.net (Stefan O'Rear) Date: Mon Jun 4 00:43:16 2007 Subject: [Xmonad] darcs patch: Remove no-longer-needed 'dimensions' state (-5 loc) Message-ID: Sun Jun 3 21:47:15 PDT 2007 Stefan O'Rear * Remove no-longer-needed 'dimensions' state (-5 loc) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/x-darcs-patch Size: 4845 bytes Desc: A darcs patch for your repository! Url : http://www.haskell.org/pipermail/xmonad/attachments/20070603/275147cf/attachment.bin From dons at cse.unsw.edu.au Mon Jun 4 00:53:32 2007 From: dons at cse.unsw.edu.au (Donald Bruce Stewart) Date: Mon Jun 4 00:49:04 2007 Subject: [Xmonad] darcs patch: Remove no-longer-needed 'dimensions' state (-5 loc) In-Reply-To: References: Message-ID: <20070604045332.GG4042@cse.unsw.EDU.AU> stefanor: > Sun Jun 3 21:47:15 PDT 2007 Stefan O'Rear > * Remove no-longer-needed 'dimensions' state (-5 loc) Applied. Thanks. -- Don From codesite-noreply at google.com Mon Jun 4 00:55:17 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Mon Jun 4 00:50:47 2007 Subject: [Xmonad] Issue 13 in project xmonad Message-ID: Issue 13: Windows not always hidden properly http://code.google.com/p/xmonad/issues/detail?id=13 Comment #1 by dons00: Proposal to fix this is to pass doLayout the Stack representing tiled windows, and to allow it to return a pair of just those windows visible, and any hidden. This should fix fullscreen mode (it would be tall (Just 1), taking 1 focused window), and two pane becomes trivial. Issue attribute updates: Status: Started 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 From codesite-noreply at google.com Mon Jun 4 00:56:43 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Mon Jun 4 00:52:14 2007 Subject: [Xmonad] Issue 16 in project xmonad Message-ID: <163600d68504320d643485c695e80@google.com> Issue 16: xmonad does not mark non-visible windows as iconafied http://code.google.com/p/xmonad/issues/detail?id=16 Comment #4 by dons00: Stefan has implement WMState support, and non-visible windows are now set iconified. 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 From codesite-noreply at google.com Mon Jun 4 00:57:50 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Mon Jun 4 00:53:22 2007 Subject: [Xmonad] Issue 10 in project xmonad Message-ID: Issue 10: UI idea: hide 'n' windows. http://code.google.com/p/xmonad/issues/detail?id=10 Comment #2 by dons00: See #13. Issue attribute updates: Status: Duplicate -- 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 From codesite-noreply at google.com Mon Jun 4 00:59:10 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Mon Jun 4 00:54:39 2007 Subject: [Xmonad] Issue 6 in project xmonad Message-ID: Issue 6: Xmonad does not respect size hints http://code.google.com/p/xmonad/issues/detail?id=6 Comment #3 by dons00: Fixed. Tiled windows have size hints ignored -- completely. They are always sized to fit the tile they're given. Floating windows have their hints respected (try 'xv' for example). 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 From sjanssen at cse.unl.edu Mon Jun 4 01:34:15 2007 From: sjanssen at cse.unl.edu (Spencer Janssen) Date: Mon Jun 4 01:29:53 2007 Subject: [Xmonad] darcs patch: Remove no-longer-needed 'dimensions' state (-5 loc) In-Reply-To: References: Message-ID: <20070604003415.43389ec7@localhost> On Sun, 03 Jun 2007 21:47:42 -0700 "Stefan O'Rear" wrote: > Sun Jun 3 21:47:15 PDT 2007 Stefan O'Rear > * Remove no-longer-needed 'dimensions' state (-5 loc) Applied, thanks. From codesite-noreply at google.com Mon Jun 4 01:43:53 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Mon Jun 4 01:39:22 2007 Subject: [Xmonad] Issue 6 in project xmonad Message-ID: <163600d8e404320e0cd654af97def@google.com> Issue 6: Xmonad does not respect size hints http://code.google.com/p/xmonad/issues/detail?id=6 Comment #4 by SpencerJanssen: This issue is not fixed. Xmonad currently respects the initial size request for floating windows, but still ignores minimum/maximum dimensions and aspect ratio hints. Issue attribute updates: Status: Accepted Owner: SpencerJanssen -- 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 From xmonad at cenderis.demon.co.uk Mon Jun 4 05:04:37 2007 From: xmonad at cenderis.demon.co.uk (Bruce Stephens) Date: Mon Jun 4 05:00:07 2007 Subject: [Xmonad] border colours In-Reply-To: <20070604011803.GA3113@cse.unsw.EDU.AU> (Donald Bruce Stewart's message of "Mon\, 4 Jun 2007 11\:18\:03 +1000") References: <874plod20b.fsf@cenderis.demon.co.uk> <20070604011803.GA3113@cse.unsw.EDU.AU> Message-ID: <87tztorsyi.fsf@cenderis.demon.co.uk> dons@cse.unsw.edu.au (Donald Bruce Stewart) writes: [...] >> focusedBorderColor = "#ff00ff" >> >> to be nicely visible. Maybe it's too obvious? > > I think this is an interesting issue. Magenta seems a bit horrible > though :-) Perhaps we can just suggest some higher visibility settings > on the web page? Yeah, it's starting to grate for me, too. Probably not suitable as a default, anyway. From A.M.Gimblett at swansea.ac.uk Mon Jun 4 06:55:48 2007 From: A.M.Gimblett at swansea.ac.uk (Andy Gimblett) Date: Mon Jun 4 06:51:18 2007 Subject: [Xmonad] Howtos wanted: Configuring xmonad with display managers In-Reply-To: <20070602180134.GA5064@jpc.example.com> References: <20070602180134.GA5064@jpc.example.com> Message-ID: <20070604105548.GC18111@cspcag2.swan.ac.uk> I'm running xmonad under FreeBSD 6.1 and Ubuntu Fiesty, both using gdm, from ~/.xsession. I'm not using any Ubuntu magic to add a new display manager menu item - I hacked this mechanism together back when FreeBSD was all I used (ie until about a month ago). The relevant part of ~/.xsession looks something like: -- dzstatus & while true ; do PICK=$(gmessage -buttons _Xmonad,_Ice,"GTK_STOCK_QUIT" -default _Xmonad -center -print "Window Manager?") case $PICK in _Xmonad) /usr/local/bin/xmonad > /dev/null 2>&1 ;; _Ice) /usr/bin/icewm ;; GTK_STOCK_QUIT) exit ;; esac done -- dzstatus is a shell script which just runs a (python) status-building script and pipes it to a dzen2. It's external to .xsession so I can easily kill/restart my status bar when tweaking. I'm using this while/gmessage mechanism for a couple of reasons. First, it's sometimes nice to have a choice of window manager, though I don't use anything other than xmonad these days of course. Second, and mainly, it allows me to exit xmonad without ending the X session, so I can restart xmonad after a rebuild. The mod-q restart mechanism doesn't work for me because if I try to install a new xmonad while the old one is running, I get: [gimbo@orb xmonad] sudo runghc Setup install Installing: /usr/local/lib/xmonad-0.2/ghc-6.6 & /usr/local/bin xmonad-0.2... *** Exception: /usr/local/bin/xmonad: copyFile: resource busy (Text file busy) No-one else seems to mention this? At first I thought it was a FreeBSD-ism, but I get the same under Ubuntu. Any thoughts? (Related: I have to manually chmod a+rx /usr/local/bin/xmonad after every install, which is annoying.) -Andy -- Andy Gimblett Computer Science Department University of Wales Swansea http://www.cs.swan.ac.uk/~csandy/ From dons at cse.unsw.edu.au Mon Jun 4 07:01:45 2007 From: dons at cse.unsw.edu.au (Donald Bruce Stewart) Date: Mon Jun 4 06:57:17 2007 Subject: [Xmonad] Howtos wanted: Configuring xmonad with display managers In-Reply-To: <20070604105548.GC18111@cspcag2.swan.ac.uk> References: <20070602180134.GA5064@jpc.example.com> <20070604105548.GC18111@cspcag2.swan.ac.uk> Message-ID: <20070604110145.GA6569@cse.unsw.EDU.AU> A.M.Gimblett: > I'm running xmonad under FreeBSD 6.1 and Ubuntu Fiesty, both using > gdm, from ~/.xsession. I'm not using any Ubuntu magic to add a new > display manager menu item - I hacked this mechanism together back when > FreeBSD was all I used (ie until about a month ago). > > The relevant part of ~/.xsession looks something like: > > -- > > dzstatus & > > while true ; do > PICK=$(gmessage -buttons _Xmonad,_Ice,"GTK_STOCK_QUIT" -default _Xmonad -center -print "Window Manager?") > case $PICK in > _Xmonad) /usr/local/bin/xmonad > /dev/null 2>&1 ;; > _Ice) /usr/bin/icewm ;; > GTK_STOCK_QUIT) exit ;; > esac > done > > -- > > dzstatus is a shell script which just runs a (python) status-building > script and pipes it to a dzen2. It's external to .xsession so I can > easily kill/restart my status bar when tweaking. > > I'm using this while/gmessage mechanism for a couple of reasons. > First, it's sometimes nice to have a choice of window manager, though > I don't use anything other than xmonad these days of course. > > Second, and mainly, it allows me to exit xmonad without ending the X > session, so I can restart xmonad after a rebuild. The mod-q restart > mechanism doesn't work for me because if I try to install a new xmonad > while the old one is running, I get: > > [gimbo@orb xmonad] sudo runghc Setup install > Installing: /usr/local/lib/xmonad-0.2/ghc-6.6 & /usr/local/bin xmonad-0.2... > *** Exception: /usr/local/bin/xmonad: copyFile: resource busy (Text file busy) > > No-one else seems to mention this? At first I thought it was a > FreeBSD-ism, but I get the same under Ubuntu. Any thoughts? Ah ha, rm -f `which xmonad` : http://xmonad.org/faq.html#config Cabal bug (imo). We should complain to the cabal guys. > (Related: I have to manually chmod a+rx /usr/local/bin/xmonad after > every install, which is annoying.) I think this was fixed in the most recent cabal. I certainly don't see it with: $ ghc-pkg list Cabal /home/dons/lib/ghc-6.6/package.conf: Cabal-1.1.7 Cheers, Don From A.M.Gimblett at swansea.ac.uk Mon Jun 4 07:08:34 2007 From: A.M.Gimblett at swansea.ac.uk (Andy Gimblett) Date: Mon Jun 4 07:04:04 2007 Subject: [Xmonad] Howtos wanted: Configuring xmonad with display managers In-Reply-To: <20070604110145.GA6569@cse.unsw.EDU.AU> References: <20070602180134.GA5064@jpc.example.com> <20070604105548.GC18111@cspcag2.swan.ac.uk> <20070604110145.GA6569@cse.unsw.EDU.AU> Message-ID: <20070604110834.GA27341@cspcag2.swan.ac.uk> On Mon, Jun 04, 2007 at 09:01:45PM +1000, Donald Bruce Stewart wrote: > > Ah ha, rm -f `which xmonad` : > > http://xmonad.org/faq.html#config D'oh! Thanks. I'm sure that wasn't in the FAQ last time I read it. ;-) > > (Related: I have to manually chmod a+rx /usr/local/bin/xmonad after > > every install, which is annoying.) > > I think this was fixed in the most recent cabal. I certainly don't see > it with: > > $ ghc-pkg list Cabal > /home/dons/lib/ghc-6.6/package.conf: > Cabal-1.1.7 Odd: I do. :-) Are you tracking Cabal darcs, or is that the stable 1.1.7? [gimbo@orb xmonad] ghc-pkg list Cabal /usr/lib/ghc-6.6/package.conf: Cabal-1.1.7 Still, thanks! -Andy -- Andy Gimblett Computer Science Department University of Wales Swansea http://www.cs.swan.ac.uk/~csandy/ From li at pps.jussieu.fr Mon Jun 4 07:47:31 2007 From: li at pps.jussieu.fr (Zheng Li) Date: Mon Jun 4 07:51:16 2007 Subject: [Xmonad] Re: reserved keyboard shortcuts References: <20070530161435.GA9290@jobbicycle.corp.yahoo.com> Message-ID: <87bqfw6iwc.fsf@gmail.com> brad clawsie writes: > after an update from darcs, i see alt-LeftArrow and alt-RightArrow are > no longer used as shortcuts, which is nice because they are used in > firefox. alt-b is still in the default, which is used to access the > firefox bookmarks menu. > > i personally maintain a private Config.hs to deal with this, not sure > if it is something worth addressing Is it possible to allow defining keys combination as the modifier? I used to be a wmii user, on which I define Ctrl-t as the modifier a la Ratpoison and Emacs. Thanks From glasser at mit.edu Mon Jun 4 08:07:54 2007 From: glasser at mit.edu (David Glasser) Date: Mon Jun 4 08:03:24 2007 Subject: [Xmonad] Howtos wanted: Configuring xmonad with display managers In-Reply-To: <20070604110145.GA6569@cse.unsw.EDU.AU> References: <20070602180134.GA5064@jpc.example.com> <20070604105548.GC18111@cspcag2.swan.ac.uk> <20070604110145.GA6569@cse.unsw.EDU.AU> Message-ID: <1ea387f60706040507y786d384evf7a6277ecb60c664@mail.gmail.com> On 6/4/07, Donald Bruce Stewart wrote: > A.M.Gimblett: > > [gimbo@orb xmonad] sudo runghc Setup install > > Installing: /usr/local/lib/xmonad-0.2/ghc-6.6 & /usr/local/bin xmonad-0.2... > > *** Exception: /usr/local/bin/xmonad: copyFile: resource busy (Text file busy) > > > > No-one else seems to mention this? At first I thought it was a > > FreeBSD-ism, but I get the same under Ubuntu. Any thoughts? > > Ah ha, rm -f `which xmonad` : Alternatively, add xmonad's build directory to your PATH, or symlink from a location in your path to the built copy, and just don't run install. --dave -- David Glasser | glasser@mit.edu | http://www.davidglasser.net/ From glasser at mit.edu Mon Jun 4 08:10:32 2007 From: glasser at mit.edu (David Glasser) Date: Mon Jun 4 08:06:02 2007 Subject: [Xmonad] Re: reserved keyboard shortcuts In-Reply-To: <87bqfw6iwc.fsf@gmail.com> References: <20070530161435.GA9290@jobbicycle.corp.yahoo.com> <87bqfw6iwc.fsf@gmail.com> Message-ID: <1ea387f60706040510x3e2567c8s93ca93361157af9c@mail.gmail.com> On 6/4/07, Zheng Li wrote: > Is it possible to allow defining keys combination as the modifier? I used to be > a wmii user, on which I define Ctrl-t as the modifier a la Ratpoison and Emacs. This isn't currently possible, although it wouldn't be too hard to write (the tricky part is running through all the windows and updating which keys are grabbed each time the current keymap is changed). Alternatively, you can look at the XMonadContrib.Commands module, which lets you run xmonad actions from a dmenu prompt; I currently only have one keybinding and run all actions through Commands. (You can be less extreme and only remove some of your keybindings of course.) --dave -- David Glasser | glasser@mit.edu | http://www.davidglasser.net/ From arcatan at kapsi.fi Mon Jun 4 09:01:59 2007 From: arcatan at kapsi.fi (Miikka Koskinen) Date: Mon Jun 4 08:57:30 2007 Subject: [Xmonad] border colours In-Reply-To: <874plod20b.fsf@cenderis.demon.co.uk> References: <874plod20b.fsf@cenderis.demon.co.uk> Message-ID: <20070604130159.GA3594@kapsi.fi> On Mon, Jun 04, 2007 at 12:58:12AM +0100, Bruce Stephens wrote: > I note that normalBorderColor is a grey, and focusedBorderColor is > red. I don't find these particularly distinguishable. I agree, and I have normal color vision. At the moment I use these settings: normalBorderColor = "#333333" -- dark grey focusedBorderColor = "#aecf96" -- light green I find these colors very appealing and easy to distinguish against black terminals. With GUI apps and their grey-colored widgets the colors do not work, but I usually use GUI apps only in fullscreen mode so it's not such a problem. I picked the latter color from some dzen screenshot by Rob, by the way. -- Miikka Koskinen, aka. arcatan From rob.manea at googlemail.com Mon Jun 4 09:05:27 2007 From: rob.manea at googlemail.com (Robert Manea) Date: Mon Jun 4 09:01:01 2007 Subject: [Xmonad] State information, workspace names and "emptyness" indicator Message-ID: <20070604130527.GA3216@deski.rob-home.homeip.net> 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 # 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. From kai.grossjohann at verizonbusiness.com Mon Jun 4 09:54:35 2007 From: kai.grossjohann at verizonbusiness.com (Kai Grossjohann) Date: Mon Jun 4 09:50:50 2007 Subject: [Xmonad] Howtos wanted: Configuring xmonad with display managers In-Reply-To: (Jeremy Shaw's message of "Sat, 02 Jun 2007 12:17:06 -0700") References: <20070602180134.GA5064@jpc.example.com> Message-ID: <86wsyjesf8.fsf@ketchup.de.uu.net> Jeremy Shaw writes: > At Sat, 2 Jun 2007 12:01:34 -0600, > Jason Creighton wrote: >> >> 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. > > For kde you can set the environment variable KDEWM=xmonad. Does anyone know what to do for Gnome? Kai From codesite-noreply at google.com Mon Jun 4 14:52:42 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Mon Jun 4 14:48:12 2007 Subject: [Xmonad] Issue 6 in project xmonad Message-ID: <163600d68504321911e2a2b2b3f37@google.com> 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 From pdewacht at gmail.com Mon Jun 4 15:47:43 2007 From: pdewacht at gmail.com (Peter De Wachter) Date: Mon Jun 4 15:43:29 2007 Subject: [Xmonad] updated size hints patch Message-ID: <878xazfqn4.wl%pdewacht@gmail.com> 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. -------------- next part -------------- A non-text attachment was scrubbed... Name: xmonad-size-hints.patch Type: application/octet-stream Size: 7637 bytes Desc: not available Url : http://www.haskell.org/pipermail/xmonad/attachments/20070604/362f2280/xmonad-size-hints.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: X11-extras-getWMNormalHints.patch Type: application/octet-stream Size: 4696 bytes Desc: not available Url : http://www.haskell.org/pipermail/xmonad/attachments/20070604/362f2280/X11-extras-getWMNormalHints.obj From droundy at darcs.net Mon Jun 4 16:37:42 2007 From: droundy at darcs.net (David Roundy) Date: Mon Jun 4 16:33:14 2007 Subject: [Xmonad] updated size hints patch In-Reply-To: <878xazfqn4.wl%pdewacht@gmail.com> References: <878xazfqn4.wl%pdewacht@gmail.com> Message-ID: <20070604203740.GJ29338@abridgegame.org> On Mon, Jun 04, 2007 at 09:47:43PM +0200, Peter De Wachter wrote: > 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. I'll point out that this feature can very easily be added as an add-on module in XMonadContrib as a layout modifier (which just post-processes an arbitrary layout). And if I ever have more time for xmonad hacking, I might do that. -- David Roundy Department of Physics Oregon State University From sjanssen at cse.unl.edu Mon Jun 4 17:05:51 2007 From: sjanssen at cse.unl.edu (Spencer Janssen) Date: Mon Jun 4 17:02:22 2007 Subject: [Xmonad] updated size hints patch In-Reply-To: <878xazfqn4.wl%pdewacht@gmail.com> References: <878xazfqn4.wl%pdewacht@gmail.com> Message-ID: <20070604160551.30db59e6@localhost> On Mon, 04 Jun 2007 21:47:43 +0200 "Peter De Wachter" wrote: > 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. > I've applied the "apply size hints to floating windows" patch -- it's really the right thing to do for apps like mplayer. I still don't think we want to handle size hints for tiled windows by default. However, as David points out, we could have some tiled layouts in XMonadContrib that use this size hint code. Thanks for submitting this patch (twice!). Cheers, Spencer Janssen From l.mai at web.de Mon Jun 4 14:22:37 2007 From: l.mai at web.de (l.mai@web.de) Date: Mon Jun 4 18:28:09 2007 Subject: [Xmonad] darcs patch: realign guard Message-ID: Mon Jun 4 20:20:45 CEST 2007 l.mai@web.de * realign guard -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/x-darcs-patch Size: 5079 bytes Desc: A darcs patch for your repository! Url : http://www.haskell.org/pipermail/xmonad/attachments/20070604/442af3ae/attachment.bin From daniel at wagner-home.com Mon Jun 4 18:56:36 2007 From: daniel at wagner-home.com (daniel@wagner-home.com) Date: Mon Jun 4 18:52:06 2007 Subject: [Xmonad] darcs patch: Contrib package for 6.4 users Message-ID: Mon Jun 4 15:55:34 PDT 2007 daniel@wagner-home.com * Contrib package for 6.4 users -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/x-darcs-patch Size: 6774 bytes Desc: A darcs patch for your repository! Url : http://www.haskell.org/pipermail/xmonad/attachments/20070604/4ce83a59/attachment.bin From codesite-noreply at google.com Mon Jun 4 19:39:48 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Mon Jun 4 19:35:16 2007 Subject: [Xmonad] Issue 6 in project xmonad Message-ID: <163600d10304321d14a3274ac11e9@google.com> 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 From dons at cse.unsw.edu.au Mon Jun 4 20:50:42 2007 From: dons at cse.unsw.edu.au (Donald Bruce Stewart) Date: Mon Jun 4 20:46:13 2007 Subject: [Xmonad] darcs patch: Contrib package for 6.4 users In-Reply-To: References: Message-ID: <20070605005042.GB5994@cse.unsw.EDU.AU> daniel: > Mon Jun 4 15:55:34 PDT 2007 daniel@wagner-home.com > * Contrib package for 6.4 users Applied. Thanks. -- Don From kai.grossjohann at verizonbusiness.com Tue Jun 5 03:31:36 2007 From: kai.grossjohann at verizonbusiness.com (Kai Grossjohann) Date: Tue Jun 5 03:27:56 2007 Subject: [Xmonad] Darcs version on Debian etch? Message-ID: <86hcpm97s7.fsf@ketchup.de.uu.net> I'm trying to compile the most recent darcs version on Debian etch, but it requires a new X11-extras, and that complains that X11 is too old (etch has X11-1.2, X11-extras requires X11-1.2.1). What is an easy way to get the new xmonad compiled on Debian? I found http://haskell-unsafe.alioth.debian.org/haskell-unsafe.html but that seems to think that stable == woody, so I am reluctant to rely on it. tia, Kai From dons at cse.unsw.edu.au Tue Jun 5 03:37:28 2007 From: dons at cse.unsw.edu.au (Donald Bruce Stewart) Date: Tue Jun 5 03:32:58 2007 Subject: [Xmonad] Darcs version on Debian etch? In-Reply-To: <86hcpm97s7.fsf@ketchup.de.uu.net> References: <86hcpm97s7.fsf@ketchup.de.uu.net> Message-ID: <20070605073728.GB9328@cse.unsw.EDU.AU> kai.grossjohann: > I'm trying to compile the most recent darcs version on Debian etch, but > it requires a new X11-extras, and that complains that X11 is too old > (etch has X11-1.2, X11-extras requires X11-1.2.1). > > What is an easy way to get the new xmonad compiled on Debian? X11-1.2.2 and X11-extras 0.2 are on hackage, but I don't think anyone has rolled .debs for them yet. Might be best to just build it with cabal, manually? -- Don From pdewacht at gmail.com Tue Jun 5 03:48:28 2007 From: pdewacht at gmail.com (Peter De Wachter) Date: Tue Jun 5 03:44:01 2007 Subject: [Xmonad] contrib patch: nicer tiled layout obeying size hints Message-ID: <87vee23kqb.wl%pdewacht@gmail.com> 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...) -------------- next part -------------- A non-text attachment was scrubbed... Name: hinted-tile.patch Type: application/octet-stream Size: 9398 bytes Desc: not available Url : http://www.haskell.org/pipermail/xmonad/attachments/20070605/26bd9446/hinted-tile-0001.obj From dons at cse.unsw.edu.au Tue Jun 5 03:55:33 2007 From: dons at cse.unsw.edu.au (Donald Bruce Stewart) Date: Tue Jun 5 03:51:02 2007 Subject: [Xmonad] contrib patch: nicer tiled layout obeying size hints In-Reply-To: <87vee23kqb.wl%pdewacht@gmail.com> References: <87vee23kqb.wl%pdewacht@gmail.com> Message-ID: <20070605075532.GA9565@cse.unsw.EDU.AU> pdewacht: > 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...) Applied. Nice idea. -- Don From kai.grossjohann at verizonbusiness.com Tue Jun 5 04:26:17 2007 From: kai.grossjohann at verizonbusiness.com (Kai Grossjohann) Date: Tue Jun 5 04:23:01 2007 Subject: [Xmonad] Darcs version on Debian etch? In-Reply-To: <20070605073728.GB9328@cse.unsw.EDU.AU> (Donald Bruce Stewart's message of "Tue, 05 Jun 2007 17:37:28 +1000") References: <86hcpm97s7.fsf@ketchup.de.uu.net> <20070605073728.GB9328@cse.unsw.EDU.AU> Message-ID: <868xay9592.fsf@ketchup.de.uu.net> dons@cse.unsw.edu.au (Donald Bruce Stewart) writes: > Might be best to just build [X11-1.2.2] with cabal, manually? It's difficult to install: $ runhaskell Setup.hs configure --prefix=$HOME [... elided ...] $ runhaskell Setup.hs build [... elided ...] $ runhaskell Setup.hs install Installing: /home/kgrossjo/lib/X11-1.2.2/ghc-6.6 & /home/kgrossjo/bin X11-1.2.2... Registering X11-1.2.2... Reading package info from ".installed-pkg-config" ... done. Unable to rename "/usr/lib/ghc-6.6/package.conf" to "/usr/lib/ghc-6.6/package.conf.old" Saving old package config file... ghc-pkg.bin: /usr/lib/ghc-6.6/package.conf: renameFile: permission denied (Permission denied) I don't like to modify system files (owned by dpkg) by self-installed software. I guess I might just install my own GHC in $HOME. But that sounds like quite a bit of work... Kai From dons at cse.unsw.edu.au Tue Jun 5 04:31:11 2007 From: dons at cse.unsw.edu.au (Donald Bruce Stewart) Date: Tue Jun 5 04:26:40 2007 Subject: [Xmonad] Darcs version on Debian etch? In-Reply-To: <868xay9592.fsf@ketchup.de.uu.net> References: <86hcpm97s7.fsf@ketchup.de.uu.net> <20070605073728.GB9328@cse.unsw.EDU.AU> <868xay9592.fsf@ketchup.de.uu.net> Message-ID: <20070605083111.GA9815@cse.unsw.EDU.AU> kai.grossjohann: > dons@cse.unsw.edu.au (Donald Bruce Stewart) writes: > > > Might be best to just build [X11-1.2.2] with cabal, manually? > > It's difficult to install: > > $ runhaskell Setup.hs configure --prefix=$HOME > [... elided ...] > $ runhaskell Setup.hs build > [... elided ...] > $ runhaskell Setup.hs install > Installing: /home/kgrossjo/lib/X11-1.2.2/ghc-6.6 & /