- xmonad - Haskell.org

Issue 73 in xmonad: xmonad as a library
by codesite-noreply＠google.com 19 Dec '07

19 Dec '07

Issue 73: xmonad as a library http://code.google.com/p/xmonad/issues/detail?id=73 Comment #5 by dons00: Documentation done. Only thing left is an example, commented-out xmonad.hs users can use as a template. Issue attribute updates: Labels: -Priority-Medium Priority-Critical -- 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

4 4

Issue 105 in xmonad: Tabs become managed windows upon xmonad restart on multi-screen setups
by codesite-noreply＠google.com 19 Dec '07

19 Dec '07

Issue 105: Tabs become managed windows upon xmonad restart on multi-screen setups http://code.google.com/p/xmonad/issues/detail?id=105 Comment #4 by lit...(a)hethrael.com: I forgot to answer your first question in comment 2 in my last reply. Yes, in tabbedbug1.png the tabs should be in the dark space above the browser window. Also, they are much taller on workspace 2 than they should be; they take up the whole green area instead of just the rectangles around the text (they act just like a window in a Tall layout should). -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 106 in xmonad: LayoutCombinators disallows custom key-bindings to work?
by codesite-noreply＠google.com 18 Dec '07

18 Dec '07

Issue 106: LayoutCombinators disallows custom key-bindings to work? http://code.google.com/p/xmonad/issues/detail?id=106 New issue report by thomas.adam22: What steps will reproduce the problem? 1. import XMonad.Layout.LayoutCombinators hiding ( (|||) ) 2. Use the sample config from the docs: myLayouts = (Tall 1 (3/100) (1/2) *//* Full) ||| (Tall 1 (3/100) (1/2) ***||** Full) ||| Full ||| etc.. main = xmonad defaultConfig { layoutHook = myLayouts } 3. Assume you hace key-bindings like this: -- window navigation keybindings. , ((modm, xK_Right), sendMessage $ Go R) , ((modm, xK_Left ), sendMessage $ Go L) , ((modm, xK_Up ), sendMessage $ Go U) , ((modm, xK_Down ), sendMessage $ Go D) What is the expected output? What do you see instead? The above key-bindings from (3) above won't work. They ought to. What version of the product are you using? On what operating system? xmonad-darcs, Ubuntu Linux (Hardy). Please provide any additional information below. I have no idea if this is some stupidity on my part in (mis-)using the LayoutCombinators module or if it is a genuine bug. I hope it's the former though. :) Tag: Component-Contrib 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

1 0

Layout.LayoutCombinators? (Was: Re: Defining Layouts)
by Thomas Adam 18 Dec '07

18 Dec '07

Hello all -- (Replying to myself might be considered bad form, but...) On 16/12/2007, Thomas Adam <thomas.adam22(a)gmail.com> wrote: > Hello all, > > Maybe this is already possible through some combination of existing > extensions, I'm not sure so I thought I would ask anyway. > > I'm not using anything fancy at the moment, just the usual layouts > defined like this: > > , layoutHook = configurableNavigation (navigateColor "#00aa00") $ > toggleLayouts (noBorders Full) $ > (smartBorders (tiled ||| Mirror tiled ||| Full)) > > Sometimes, when I am working in tiled mode, I might have a layout such as this: > > +------------+-------------+ > | window A | | > +------------+Window D| > | window B | | > +------------+-------------+ > | window C |Window E | > +------------+-------------+ > > Where windows A,B and C are in the master pane. Is it possible to > make window D in this example fill the entire right hand side (to > effectively "cover" window E) and then to toggle it back afterwards? > There are times where there might be many more windows in the > non-master pane and having one window fill the entire space would be > useful. So I dug about a bit and had a look at: XMonad.Layout.LayoutCombinators Is this something I could conceivably use to achieve the above? I tried the example config supplied in the documentation but I confess I have no idea quite what all the weird idiomatic operators this hook defines actually means. Also, in using the example from its documentation, I noticed that none of my key-bindings worked anymore. I could still use the defaults though. Switching back to my old layout solved this, so this *has* to be a bug with LayoutCombinators. -- Thomas Adam

1 0

Issue 105 in xmonad: Tabs become managed windows upon xmonad restart on multi-screen setups
by codesite-noreply＠google.com 18 Dec '07

18 Dec '07

Issue 105: Tabs become managed windows upon xmonad restart on multi-screen setups http://code.google.com/p/xmonad/issues/detail?id=105 Comment #3 by lit...(a)hethrael.com: Yes, my Mod+Q is bound to "broadcastMessage ReleaseResources >> restart (Just "xmonad") True". I am using a slightly-modified version of Template_Config.hs from the xmonad wiki, but I have created a minimal config that exhibits the bug: import XMonad import XMonad.Layout.Tabbed main = xmonad defaultConfig { layoutHook = tabbed shrinkText defaultTConf } Although with a tabbed layout on each screen, it's even stranger: after testing the bug with the minimal config above, I switched back to my config and I'm unable to get rid of the extra empty spaces (like in tabbedbug2.png) by Mod+Space, Mod+Shift+Space, or Mod+Q. (I haven't tried Mod+Shift+C 'cause I don't want to restart my X session at the moment; I just banished the extra windows to an unused workspace.) I'm not sure that they are real windows; they're the same color as my root window, no border appears around them, and I cannot focus them with the mouse. Of course, they are secondary to the tabbed bug and might not matter. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Re: [xmonad] 0.5 and packages
by Joachim Breitner 18 Dec '07

18 Dec '07

Hi, Am Montag, den 17.12.2007, 23:07 -0800 schrieb Don Stewart: > Hey, > > Any sight of an xmonad 0.5 package yet? We're losing ground with xmonad > on debian, due to the lack of a 0.5 package I think (people building > their own or not at all). > > http://people.debian.org/~igloo/popcon-graphs/index.php?packages=xmonad%2Ca… > > The gentoo guys and arch have just gone ahead (gentoo with cabal 1.2.3, > and arch with ghc 6.8.x). Any thoughts on how best to move debian > forward? Well, I’m still waiting for Igloo for the new ghc6.8 packages. He said that he will look for shortly, but he hasn’t done it yet. The quickest move for debian, besides having the new ghc packages in place, would be a version of xmonad and X11 1.4 that compiles with the old Cabal version, but I’m not sure if such a hack is worth the effort. Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nomeata(a)debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nomeata(a)joachim-breitner.de | http://people.debian.org/~nomeata

2 1

Dzen Wiki
by Robert Manea 18 Dec '07

18 Dec '07

Hello, I'm just writing to inform you that dzen's wiki has moved to: http://dzen.geekmode.org/wiki/wiki.cgi/-main/ I will keep a permanent redirect from the old site for some time, though. The wiki is open for everyone, so please feel free to extend and enhance it. Bye, Rob.

2 2

Issue 105 in xmonad: Tabs become managed windows upon xmonad restart on multi-screen setups
by codesite-noreply＠google.com 18 Dec '07

18 Dec '07

Issue 105: Tabs become managed windows upon xmonad restart on multi-screen setups http://code.google.com/p/xmonad/issues/detail?id=105 Comment #2 by andrea.rossato: sorry for my previous comment, now I see: in the first image the 2 decorations are indeed in workspace 2 (they should be in workspace 1) as in the image 2. right? still I must ask again: are you sure that "broadcastMessage ReleaseResources" is sent before restarting? andrea -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 90 in xmonad: Restarting xmonad re-runs dzen/xmobar, which puts it at the top of the window stack
by codesite-noreply＠google.com 18 Dec '07

18 Dec '07

Issue 90: Restarting xmonad re-runs dzen/xmobar, which puts it at the top of the window stack http://code.google.com/p/xmonad/issues/detail?id=90 Comment #2 by andrea.rossato: now, xmonad does not run anything and so it is not xmonad that is starting another instance of xmobar or dzen.. so probably you are experiencing some issues with you Xsession startup script. Is this related to documentation you read - that documentation could be indeed bugged? For xmobar, you can use the standard input reader: when xmonad quits xmobar is going to quit too. Have a look at XMonad.Config.Sjanssen (of the xmonad-contrib library) for a working example. I would suggest to mark this report as invalid. Thanks Andrea -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 105 in xmonad: Tabs become managed windows upon xmonad restart on multi-screen setups
by codesite-noreply＠google.com 18 Dec '07

18 Dec '07

Issue 105: Tabs become managed windows upon xmonad restart on multi-screen setups http://code.google.com/p/xmonad/issues/detail?id=105 Comment #1 by andrea.rossato: I'm sorry but I cannot fully understand this bug report. According to the status bar, in the focused workspace of the attached images, there is the Tall layout, and not the tabbed layout. "Closing one of the tab windows quits xmonad": what are the tab windows you are referring to? the decoration windows (the tabs) or the window the decoration is for? I don't see any decoration becoming managed in you screenshot. sorry if I'm asking this info: I'm supposed to be the maintainer of the tabbed layout, but I don't have multiple screens I can use to reproduce you problem, so I need more information... by the way, mod+q should issue this command: broadcastMessage ReleaseResources >> restart (Just "xmonad") True did you change it? specifically "broadcastMessage ReleaseResources" should destroy all decoration, so no decoration should be managed after a xmonad restart. Thanks Andrea -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0