January 2010 - xmonad

Issue 328 in xmonad: RunOrRaise and dbus(?)
by codesite-noreply＠google.com 04 Sep '11

04 Sep '11

Status: New Owner: ---- New issue 328 by grapescan: RunOrRaise and dbus(?) http://code.google.com/p/xmonad/issues/detail?id=328 What steps will reproduce the problem? 1. Set some bindings like this: ("M-t", runOrRaise "transmission" (className =? "Transmission")) or ("M-w", runOrRaise "firefox" (className =? "Shiretoko")) 2. Try to run these programs with created shortcuts 3. Try to run these programs without created shortcuts (i.e. from terminal or gmrun) What is the expected output? What do you see instead? Starting from terminal or gmrun looks fine while using shortcuts causes strange behavior. Firefox complains about connecting to session: "/usr/bin/dbus-launch terminated abnormally without any error message". Transmission doesn't want to open torrents from Firefox (torrents opened with Transmission from web-browser). It says something like "Transmission is already started." What version of the product are you using? On what operating system? I use actual version of ArchLinux. I checked dbus packages - they seem to be OK. Packages xmonad-darcs and xmonad-contrib-darcs built a few weeks ago. Attachments: xmonad.hs 5.3 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 3

Re: Issue 322 in xmonad: Background shown when workspace switches
by codesite-noreply＠google.com 17 Aug '11

17 Aug '11

Comment #2 on issue 322 by sgsoftware: Background shown when workspace switches http://code.google.com/p/xmonad/issues/detail?id=322 I am not sure that this is strictly an X server problem since I've got similar behavior after upgrading xmonad from version 0.8.1 to version 0.9. Apparently something has changed in between and now xmonad draws background so that it is very noticeable (and quite annoying). In the previous version of xmonad switching between two full-screen windows was immediate and I could see no background. -- 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 6

Issue 325 in xmonad: Layout.Spacing breaks Layout.WindowNavigation
by codesite-noreply＠google.com 15 Aug '11

15 Aug '11

Status: New Owner: ---- New issue 325 by OrbisVicis: Layout.Spacing breaks Layout.WindowNavigation http://code.google.com/p/xmonad/issues/detail?id=325 Removing the spacing modifier in the layoutHook or setting "spacing 0" fixes the problem. Symptoms: While Go or Swap *might* initially work, they very quickly lock up and do nothing. -- 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 9

Issue 359 in xmonad: shellPromptHere from XMonad.Actions.SpawnOn doesn't work as claimed
by codesite-noreply＠google.com 05 Aug '11

05 Aug '11

Status: New Owner: ---- New issue 359 by wei.hoo: shellPromptHere from XMonad.Actions.SpawnOn doesn't work as claimed http://code.google.com/p/xmonad/issues/detail?id=359 What steps will reproduce the problem? 1. Bind a key combination to shellPromptHere 2. On workspace 1, spawn a slow-starting program, say opera, using shellPromptHere 3. Switch to workspace 2 What is the expected output? The program is placed on workspace 1 where I started the program. What do you see instead? The program shows up on the current workspace, #2. What version of the product are you using? On what operating system? xmonad-darcs and xmonad-contrib-darcs on Arch Linux. Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". Please provide any additional information below. As a general question, how do I go about debugging issues like this? In particular, how do I write out debugging information to files/console/screen? Attachments: xmonad.hs 6.8 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 9

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

Re: Issue 313 in xmonad: Merge contrib's isFullscreen and doFullFloat to core
by codesite-noreply＠google.com 07 May '11

07 May '11

Comment #6 on issue 313 by gwern0: Merge contrib's isFullscreen and doFullFloat to core http://code.google.com/p/xmonad/issues/detail?id=313 The next release from darcs will be 1.0; is there any particular reason the change hasn't been made & pushed, or this bug closed? -- 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

Re: Issue 317 in xmonad: Implement a working X.U.putSelection
by codesite-noreply＠google.com 10 Mar '11

10 Mar '11

Comment #22 on issue 317 by wirtwo...(a)gmail.com: Implement a working X.U.putSelection http://code.google.com/p/xmonad/issues/detail?id=317 Issue 365 has been merged into this issue. -- 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 7

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