- xmonad - Haskell.org

Issue 275 in xmonad: XMonad.Contrib.Loggers.battery creates zombie sh if acpi not installed
by codesite-noreply＠google.com 17 Feb '09

17 Feb '09

Updates: Status: Invalid Comment #2 on issue 275 by roma(a)ro-che.info: XMonad.Contrib.Loggers.battery creates zombie sh if acpi not installed http://code.google.com/p/xmonad/issues/detail?id=275 This problem is absent in darcs. -- 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 275 in xmonad: XMonad.Contrib.Loggers.battery creates zombie sh if acpi not installed
by codesite-noreply＠google.com 17 Feb '09

17 Feb '09

Comment #1 on issue 275 by dyfrgi: XMonad.Contrib.Loggers.battery creates zombie sh if acpi not installed http://code.google.com/p/xmonad/issues/detail?id=275 Component-Contrib -- 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 275 in xmonad: XMonad.Contrib.Loggers.battery creates zombie sh if acpi not installed
by codesite-noreply＠google.com 17 Feb '09

17 Feb '09

Status: New Owner: ---- New issue 275 by dyfrgi: XMonad.Contrib.Loggers.battery creates zombie sh if acpi not installed http://code.google.com/p/xmonad/issues/detail?id=275 What steps will reproduce the problem? 1. Set up dzen with a ppExtras array containing battery 2. Ensure that the 'acpi' binary is not present on the system, or is not in the PATH 3. Run xmonad What is the expected output? What do you see instead? I'd expect an error to be flagged or nothing to happen. Instead, I get zombie sh processes. What version of the product are you using? On what operating system? xmonad 0.8.1, xmonad-contrib 0.8.1 Please provide any additional information below. This can obviously be worked around by simply not using the battery logger if the acpi utility is not installed, or by installing the acpi utility, but the behavior in this error case is undesirable. -- 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 274 in xmonad: Please provide link to sources in documentation
by codesite-noreply＠google.com 16 Feb '09

16 Feb '09

Status: New Owner: ---- New issue 274 by alexey.skladnoy: Please provide link to sources in documentation http://code.google.com/p/xmonad/issues/detail?id=274 What steps will reproduce the problem? 1. Go to http://xmonad.org/xmonad-docs/xmonad/ 2. Browse documentation, try to find link to module source. None. What is the expected output? What do you see instead? I'd like to have links to colorized source of module like http://haskell.org/ghc/docs/6.8.3/html/libraries/base/Data-List.html This is very handy if one want to look under hood. I'm no haddock expert but I presume it must be close to trivial. Please provide any additional information below. -- 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 91 in xmonad: DynamicLog causes xmonad to hang when the output pipe is full
by codesite-noreply＠google.com 16 Feb '09

16 Feb '09

Comment #6 on issue 91 by wirtwolff: DynamicLog causes xmonad to hang when the output pipe is full http://code.google.com/p/xmonad/issues/detail?id=91 Ugh, should have warned, if you're going to do this it's convenient to use a workspace full of terminals in which you've already got pipe catting commands in shell history, since mouse will no longer copy paste. Also, after my response to the fedora 10 blog post a different xmonad user emailed me that this pipe issue had been extremely frustrating for him. Probably our documentation and awareness of the issue is better at this point than when he was looking for help, but my impression is it bites more people than we think. -- 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 91 in xmonad: DynamicLog causes xmonad to hang when the output pipe is full
by codesite-noreply＠google.com 16 Feb '09

16 Feb '09

Comment #5 on issue 91 by wirtwolff: DynamicLog causes xmonad to hang when the output pipe is full http://code.google.com/p/xmonad/issues/detail?id=91 Hmm, unfortunately, looks like this needs to be re-opened. Run either of these configs with latest darcs, or Config.Sjanssen, or anything that spawnPipes and hPutStrLn's to a status bar. Then kill the bar and hold down mod-j till xmonad freezes. Asgaroth worked out can find pipe fd via lsof, so to clear it to restart xmonad can use something like: ls /proc/`pgrep xmonad`/fd/`lsof | grep xmonad | \ egrep '[ur] *FIFO' | sed -n 's/.*$[0-9]$[ur].*/\1/ p'` and cat the appropriate pipe. import XMonad import XMonad.Hooks.DynamicLog {- import XMonad.Hooks.ManageDocks import XMonad.Util.Run import System.IO main = do h <- spawnPipe "xmobar" xmonad $ defaultConfig { layoutHook = avoidStruts $ layoutHook defaultConfig , logHook = dynamicLogWithPP $ xmobarPP { ppOutput = hPutStrLn h } } -} -- or equivalent plus kebinding-- main = xmonad =<< statusBar "xmobar" xmobarPP strutkey defaultConfig where strutkey (XConfig {modMask = modm}) = (modm, xK_b) -- 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

darcs patch: L.Cross: clarify documentation and fix for haddock
by Wirt Wolff 16 Feb '09

16 Feb '09

Sun Feb 15 14:23:46 MST 2009 wirtwolff(a)gmail.com * L.Cross: clarify documentation and fix for haddock This is a fuller revision of Cross documentation as an alternative to the CrossDoc.dpatch, since there were some typos and clarifications worth taking care of along with the !Rational -- ^ comments haddock chokes on.

1 0

Issue 261 in xmonad: Fullscreen flash movie fails
by codesite-noreply＠google.com 16 Feb '09

16 Feb '09

Comment #7 on issue 261 by vic.fryzel: Fullscreen flash movie fails http://code.google.com/p/xmonad/issues/detail?id=261 I'd just like to note that I can also reproduce 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 0

Re: [Haskell-cafe] A day with xmonad
by Wirt Wolff 16 Feb '09

16 Feb '09

Excerpts from Colin Paul Adams's message of Sun Feb 15 03:10:52 -0700 2009: > I have blogged my experience of trying out xmonad with Fedora 10 at > http://colina.demon.co.uk/?q=node/534 . I'm sorry your first experiences with xmonad were so frustrating. Replacing metacity on fedora 10 is apparently a bit unique. Many people are running xmonad with Gnome smoothly on a variety of distros, including at least one on fedora 10, so I'm guessing this is probably a configuration, packaging and documentation issue. This thread on the xmonad mailing list discusses fedora 10 xmonad setup: http://article.gmane.org/gmane.comp.lang.haskell.xmonad/6557 It is linked from the xmonad wiki Gnome setup guide [1], but it would certainly be much nicer to have an actual 'Fedora 10 XMonad Setup Guide', or even better, to have xmonad packaged to "just work" on fedora. Any fedora xmonad users interested in packaging? Another possibility, (although not applicable if using Config.Gnome or the default Hooks.DynamicLog status bar functions,) is this issue with writing to unread pipes in the logHook. [2] [1] http://haskell.org/haskellwiki/Xmonad/Using_xmonad_in_Gnome#Fedora_10_and_f… [2] http://code.google.com/p/xmonad/issues/detail?id=91 regards, -- wmw

1 0

Issue 273 in xmonad: Binding multiple keys to the same keysym fails for xmonad hotkeys
by codesite-noreply＠google.com 16 Feb '09

16 Feb '09

Status: New Owner: ---- New issue 273 by sveina: Binding multiple keys to the same keysym fails for xmonad hotkeys http://code.google.com/p/xmonad/issues/detail?id=273 What steps will reproduce the problem? 1. Bind multiple physical keys to one keysym 2. Bind that keysym to some xmonad action 3. Observe that only one key works What is the expected output? What do you see instead? All keys should execute the same action, not just one. Please provide any additional information below. The error is due to XKeysymToKeycode only returning one code per key. The attached patch works around this by using XKeycodeToKeysym instead, building a mapping of keycodes to keysyms by scanning all (248) possible keycodes. Attachments: keycode.patch 6.2 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