December 2009 - xmonad

Re: Issue 189 in xmonad: MultiToggle to Full and tabbed layout makes X crusn
by codesite-noreply＠google.com 27 Jun '11

27 Jun '11

Updates: Status: Accepted Labels: Component-Contrib Comment #3 on issue 189 by byorgey: MultiToggle to Full and tabbed layout makes X crusn http://code.google.com/p/xmonad/issues/detail?id=189 I can still reproduce this. Yeesh. MultiToggle and Tabbed are both made of black magic. -- 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 8

Re: Issue 175 in xmonad: Click on unfocused window eaten
by codesite-noreply＠google.com 25 May '11

25 May '11

Comment #5 on issue 175 by scuz.there: Click on unfocused window eaten http://code.google.com/p/xmonad/issues/detail?id=175 Anybody know if this is possible? I'm gona try looking around but my Haskell knowledge is quite basic so I'm not expecting much. -- 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 3

updating.... in xmobar
by Jacob Alexandersson 04 Feb '11

04 Feb '11

Hey all, I just started trying xmonad out, and I really ilke it. I've used ratpoison in the past but eventually gave it up. xmonad seems to work better for me so far. I realize this is a xmobar question, but I am guessing there are people on this list that uses xmobar also. I have a .xmobarrc which looks like follows: <snip> Config { font = "-*-Fixed-Bold-R-Normal-*-13-*-*-*-*-*-*-*" , bgColor = "black" , fgColor = "grey" , position = TopW L 100 , lowerOnStart = True , commands = [ Run Cpu ["-L","3","-H","50","--normal","green","--high","red"] 10 , Run Memory ["-t","Mem: <usedratio>%"] 10 , Run Swap [] 10 , Run Date "%a %b %_d %l:%M" "date" 10 , Run Com "uname" ["-s","-r"] "blaj" 36000 , Run StdinReader ] , sepChar = "%" , alignSep = "}{" , template = "%StdinReader% }{ %blaj% %cpu% | %memory% * %swap% <fc=#ee9a00>%date%</fc>" } </snip> ...and in ~/.xmonad/xmonad.hs I have: <snip> ... xmproc <- spawnPipe "/usr/bin/xmobar /home/jcx/.xmobarrc" ... </snip> All I get is "updating..." where %StdinReader% is placed. Is this correct?? Am I missing something? cheers, Jacob.

3 3

Re: Issue 291 in xmonad: Layout.Tabbed has drawing problems when used with Layout.MultiToggle
by codesite-noreply＠google.com 04 Nov '10

04 Nov '10

Updates: Labels: Type-Defect Component-Contrib Comment #1 on issue 291 by vogt.adam: Layout.Tabbed has drawing problems when used with Layout.MultiToggle http://code.google.com/p/xmonad/issues/detail?id=291 Can you still reproduce this if you include this patch: Sat Dec 19 19:47:33 EST 2009 Tomas Janousek <tomi(a)nomi.cz> * Fix MultiToggle crashes with decorated layouts The problem was that certain layouts keep their "world" state in their value, which was thrown away and forgotten after ReleaseResources during toggle. In particular, decorated layouts store some X11 handles in them and allocate/deallocate it as appropriate. If any modification to their state is ignored, they may try to deallocate already deallocated memory, which results in a crash somewhere inside Xlib. This patch makes Transformers reversible so that nothing is ever ignored. As a side effect, layout transformers now do receive messages and messages for the base layout do not need the undo/reapply cycle -- we just pass messages to the current transformed layout and unapply the transformer when needed. (This, however, doesn't mean that the base layout is not asked to release resources on a transformer change -- we still need the transformer to release its resources and there's no way to do this without asking the base layout as well.) -- 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 5

Re: Issue 197 in xmonad: Blocking on nextEvent stops other threads from running
by codesite-noreply＠google.com 04 Nov '10

04 Nov '10

Comment #4 on issue 197 by byorgey: Blocking on nextEvent stops other threads from running http://code.google.com/p/xmonad/issues/detail?id=197 What's the status of this ticket? Is this a WontFix? Or is there something that could be improved here? -- 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 4

Re: Issue 4 in xmonad: Separate focus for tiled and floating layers
by codesite-noreply＠google.com 16 Oct '10

16 Oct '10

Comment #16 on issue 4 by scuz.there: Separate focus for tiled and floating layers http://code.google.com/p/xmonad/issues/detail?id=4 It might be more useful to have transients for a window hidden when that window is not focused. Similar to Photoshop on Mac. -- 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 8

Re: Issue 311 in xmonad: using noBorders on tabbed layout freezes tab bar on workspace change
by codesite-noreply＠google.com 12 Sep '10

12 Sep '10

Updates: Status: Accepted Labels: Type-Defect Component-Contrib Comment #5 on issue 311 by byorgey: using noBorders on tabbed layout freezes tab bar on workspace change http://code.google.com/p/xmonad/issues/detail?id=311 (No comment was entered for this change.) -- 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 2

Issue 336 in xmonad: xmonad won't start: Irrefutable pattern failed for pattern (Data.Maybe.Just nbc_)
by codesite-noreply＠google.com 26 Aug '10

26 Aug '10

Status: New Owner: ---- New issue 336 by flazzarino: xmonad won't start: Irrefutable pattern failed for pattern (Data.Maybe.Just nbc_) http://code.google.com/p/xmonad/issues/detail?id=336 What steps will reproduce the problem? 1. last line of ~/.xinitrc: exec /Users/franco/.cabal/bin/xmonad What is the expected output? What do you see instead? I expect to have xmonad launch but i get this error in console 11/13/09 2:36:51 PM org.x.startx[7572] xmonad-i386-darwin: XMonad/Main.hsc:(82,14)-(84,41): Irrefutable pattern failed for pattern (Data.Maybe.Just nbc_) What version of the product are you using? On what operating system? xmonad 0.9 (installed via cabal) ghc-version (6.10.4) installed via the package OSX 10.6.2 (Snow Leopard) Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". import XMonad main = xmonad defaultConfig #no output Please provide any additional information below. on a mailing list i've seen hints that X cannot support the colors gray and red but i'm using a very stock snow leopard X11, only fullscreen is turned on -- 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 10

Issue 349 in xmonad: Chromium gives BadWindow (invalid Window parameter)
by codesite-noreply＠google.com 02 Aug '10

02 Aug '10

Status: New Owner: ---- New issue 349 by ninternity: Chromium gives BadWindow (invalid Window parameter) http://code.google.com/p/xmonad/issues/detail?id=349 What steps will reproduce the problem? 1. Using the Chromium package, "chromium-browser" What is the expected output? A running chromium instance. What do you see instead? The program 'chromium-browser' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 116 error_code 3 request_code 20 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) What version of the product are you using? On what operating system? xmonad 0.9, installed from Hackage Xubuntu 9.10 Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". Please provide any additional information below. Error does not happen when using xfce + Xubuntu 9.10, nor in xmonad 0.9 + Xubuntu 9.04. Chromium version: 4.0.267.0~svn20091208r34059-0ubuntu1~ucd1~karmic Attachments: xmonad.hs 1.6 KB xmonad_recompile_out 238 bytes -- 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 1

Issue 333 in xmonad: mplayer doesn't go fullscreen
by codesite-noreply＠google.com 28 Jul '10

28 Jul '10

Status: New Owner: ---- New issue 333 by polux2001: mplayer doesn't go fullscreen http://code.google.com/p/xmonad/issues/detail?id=333 What steps will reproduce the problem? 1. install ubuntu 9.10 2. cabal install xmonad 3. mplayer somevideo 4. press F What is the expected output? What do you see instead? Nothing happens. This doesn't occur with other WM (metacity). Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". I'm using a customized xmonad.hs but the problem occurs with Config.hs found in he distribution. -- 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 13