- xmonad - Haskell.org

Issue 179 in xmonad: Tabbed Layout doesn't scale as well as it could
by codesite-noreply＠google.com 01 May '08

01 May '08

Issue 179: Tabbed Layout doesn't scale as well as it could http://code.google.com/p/xmonad/issues/detail?id=179 Comment #6 by SpencerJanssen: Yes, this patch seems to help the situation greatly, thanks. Tabbed still seems slightly sluggish compared to other layouts, but it is certainly usable now. As such I'm changing the description of the bug and leaving it open if someone wants to address any other outstanding performance issues. Regarding comment deletion: this bug tracker is intended only for constructive discussion of issues with xmonad. Andrea, the problem with your comment (and some other comments in the past) is that you mix constructive contributions with flamebait and emotional judgements. Feel free to continue using this bug tracker as long as you stick to concrete problems and solutions for xmonad, and leave the editorializing out. That is all I'd like to say here, any other discussion on this issue should go to Don and I directly or the mailing list, as the bug tracker isn't really the proper place. Issue attribute updates: Summary: Tabbed Layout doesn't scale as well as it could Labels: -Type-Defect -Priority-Medium Type-Enhancement Priority-Low -- 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 179 in xmonad: Tabbed Layout does not scale for >50 windows
by codesite-noreply＠google.com 01 May '08

01 May '08

Issue 179: Tabbed Layout does not scale for >50 windows http://code.google.com/p/xmonad/issues/detail?id=179 Comment #5 by clem...(a)endorphin.org: Thank you andrea. Your patch practically fixed the problem for me. There still seems to be an issue that makes this non-linear, but at least xmonad recovers now from the shocking event that firefox-session-resume throws 50 windows at it at once (it takes about 5-6 seconds to get back to normal even on my old box). With respect to the censoring issue, I first assumed an error as I never though your comment was intentionally censored. But yes it was. For the innocent bystander, here is the original comment of andrea http://article.gmane.org/gmane.comp.lang.haskell.xmonad/5337 Yes, there is some flame bait in this post (first paragraph). But the signal/noise ratio is definitely OK, especially as andrea is the first that seriously had a look at the problem. To me, the taunting remarks in the first paragraph are no justification for censoring this comment. Remember, this is the free software world. In theory, we don't censor. In practice we just censor much later than the rest. -- 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 179 in xmonad: Tabbed Layout does not scale for >50 windows
by codesite-noreply＠google.com 01 May '08

01 May '08

Issue 179: Tabbed Layout does not scale for >50 windows http://code.google.com/p/xmonad/issues/detail?id=179 Comment #4 by andrea.rossato: > I don't know if they are meaningful, this is why I'm posting them > here. If they indeed are, then they are also a bit puzzling. They are far from being puzzling if you just think a bit about them... and indeed after thinking a bit about them I found the problem. And the solution. Please give the attached patch a try. You'll see that by adding a bit of complexity to our decoration algorithm we can actually fix the bug... oh yes, there was a bug. Old style debugging. ps: I see that the xmonad developers keep deleting my comments - probably this patch will be shortly removed too. I don't know if they think of doing something good to their users, and to their project. Anyhow, this sort of stupid behavior (it is called censorship here) should give you a hint about the level of trust you should accord to the window manager you are running. Attachments: 179_fix.dpatch 60.7 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

1 0

Issue 97 in xmonad: xmonad stops responding to keyboard input after running xscreensaver
by codesite-noreply＠google.com 30 Apr '08

30 Apr '08

Issue 97: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 Comment #10 by YitzGale: Perhaps this is related to #184, and the thread at: http://www.haskell.org/pipermail/xmonad/2008-April/005545.html There xmonad stops responding to the keyboard (sometimes) when I press mod-shift-q a second time during a slow recompile. -- 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 185 in xmonad: XMonad.Config.Gnome
by codesite-noreply＠google.com 30 Apr '08

30 Apr '08

Issue 185: XMonad.Config.Gnome http://code.google.com/p/xmonad/issues/detail?id=185 Comment #7 by YitzGale: > can I delegate XMonad.Config.KDE to you? Well, I'll give it a try. But there are a few caveats: 1. I am an xmonad newbie. 2. My desktop machine has been very flaky lately. During the past week or so it started working again. But if it dies again, I'm stuck. It is hard to test KDE config on a MacBook (No, don't tell me how to run KDE on my MacBook, I won't do it.) > I've already got a small start on XMonad.Config.Gnome which you can copy. Yes, please, that's very important. Thank you. -- 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 185 in xmonad: XMonad.Config.Gnome
by codesite-noreply＠google.com 30 Apr '08

30 Apr '08

Issue 185: XMonad.Config.Gnome http://code.google.com/p/xmonad/issues/detail?id=185 Comment #6 by nomeata: > > There recently has been talk about being able to > > configure the KDE Pager to work with xmonad - > > to switch desktops, and to focus a window. But > > I don't know how to do that. > This is new in the darcs version of contrib, see ewmhDesktopsLayout. Actually, that’s already in the released 0.7 version. -- 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 185 in xmonad: XMonad.Config.Gnome
by codesite-noreply＠google.com 30 Apr '08

30 Apr '08

Issue 185: XMonad.Config.Gnome http://code.google.com/p/xmonad/issues/detail?id=185 Comment #5 by SpencerJanssen: YitzGale: Since you seem to be familiar with KDE, can I delegate XMonad.Config.KDE to you? I've already got a small start on XMonad.Config.Gnome which you can copy. > There recently has been talk about being able to > configure the KDE Pager to work with xmonad - > to switch desktops, and to focus a window. But > I don't know how to do that. This is new in the darcs version of contrib, see ewmhDesktopsLayout. -- 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 175 in xmonad: Click on unfocused window eaten
by codesite-noreply＠google.com 30 Apr '08

30 Apr '08

Issue 175: Click on unfocused window eaten http://code.google.com/p/xmonad/issues/detail?id=175 Comment #2 by vorner: I know it's intentional, this should have been a wish, not defect, but this google Bugzilla thing does not seem to offer me the choice. Is it possible to reopen it and set it on your side? (Maybe I should write on some google support). Thanks -- 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

2 1

Issue 179 in xmonad: Tabbed Layout does not scale for >50 windows
by codesite-noreply＠google.com 30 Apr '08

30 Apr '08

Issue 179: Tabbed Layout does not scale for >50 windows http://code.google.com/p/xmonad/issues/detail?id=179 Comment #3 by andrea.rossato: While I wonder how long it took to the xmonad algorithm complexity calculation team to lay out the math their O notated conclusions are based on (actually I'd really love to see that math too), still I'm sure the decoration module rewrite group formed within the xmonad developer team is going to take ages, literally, to reach an agreement with the tabbed module maintaining team on how to prototype a new decoration algorithm, given the constrains set out by the ACC team. Which is unfortunate for the casual xmonad user who needs to open 50-100 windows on the same workspace, quite typical for this kind of geek. Sadly I cannot be of any help. Still I was a bit amazed by the fact that iterating over such a short list of integers could lead to such a slow down - and even though I'm running a version of tabbed which has not been bloated with all the bottom, top, always, sometimes code, still I can reproduce your problem. So I decided to spend half an hour and did some math too. You know, not that scientifically sounded kind of proof a real haskeller would be able to do, but just some stupid old fashioned debugging, something even a LUA coder would be able to do: 1. I created a simple function to print out the time, with picoseconds (requires System.Time and System.IO): printNow :: String -> X () printNow s = do t <- io (toCalendarTime =<< getClockTime) io $ hPutStrLn stderr $ s ++ " - " ++ show (ctSec t) ++ "." ++ show (ctPicosec t) 2. Then I wrote a small layout modifier: data Debug a = Debug String deriving (Show, Read) instance LayoutModifier Debug Window where redoLayout (Debug s) _ _ wrs = do printNow s return (wrs, Nothing) 3. In .xmonad/xmonad.hs I wrote: main = xmonad defaultConfig {layoutHook = ModifiedLayout (Debug "tabbed") myTab } myTab = decoration shrinkText defaultTheme Tabbed (ModifiedLayout (Debug "Simplest") Simplest) I also called printNow at the very end of XMonad.Operations.windows. So we print the time: a. right after Simplest returned b. right after myTab returned c. at the end of the windows call. below there are the numbers of a few runs with enough tabs to slow everything down. I don't know if they are meaningful, this is why I'm posting them here. If they indeed are, then they are also a bit puzzling. If someone comes up with an idea on how to isolate the problem, please drop me a line. Historically I can say that from 0.4 up to 0.6 no changes have been made to tabbed and related code. The text size calculation code has been there from the very beginning of a tabbed layout (0.3 for sure) without changes. Anyway I think there's room for further investigation before calling for a rewrite (a tabbed layout with O(n) is something I'd really like to read, but I don't know if in that far future I'll still remember how to read Haskell). The numbers: Simplest - 57.187047000000 tabbed - 57.272167000000 Operations - 57.356136000000 Simplest - 57.356837000000 tabbed - 57.422710000000 Operations - 57.523055000000 Simplest - 57.523762000000 tabbed - 57.599250000000 Operations - 57.686736000000 Simplest - 59.65497000000 tabbed - 59.119980000000 Operations - 59.141826000000 Simplest - 1.672190000000 tabbed - 1.723279000000 Operations - 1.745065000000 Simplest - 3.152586000000 tabbed - 3.205879000000 Operations - 3.227333000000 Simplest - 5.839898000000 tabbed - 5.889285000000 Operations - 5.913992000000 Simplest - 5.914665000000 tabbed - 5.969013000000 Operations - 6.12130000000 Simplest - 6.12793000000 tabbed - 6.67688000000 Operations - 6.97815000000 Simplest - 6.98518000000 tabbed - 6.225578000000 Operations - 6.263437000000 Simplest - 6.264132000000 tabbed - 6.319227000000 Operations - 6.356627000000 Simplest - 6.357312000000 tabbed - 6.411805000000 Operations - 6.451679000000 Simplest - 7.712861000000 tabbed - 7.763174000000 Operations - 7.805636000000 Simplest - 7.806320000000 tabbed - 7.860956000000 Operations - 7.905911000000 Simplest - 7.906581000000 tabbed - 7.962566000000 Operations - 8.23426000000 if you want more you know how to do it. -- 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 175 in xmonad: Click on unfocused window eaten
by codesite-noreply＠google.com 30 Apr '08

30 Apr '08

Issue 175: Click on unfocused window eaten http://code.google.com/p/xmonad/issues/detail?id=175 Comment #3 by nomeata: I agree that this is a valid wishlist bug, so I’m tagging it as such. Issue attribute updates: Status: Accepted Cc: nomeata Labels: -Type-Defect Type-Enhancement -- 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