September 2013 - xmonad

Re: [xmonad] Issue 556 in xmonad: xmonad-contrib fails to install on osx
by codesite-noreply＠google.com 25 Sep '13

25 Sep '13

Updates: Summary: xmonad-contrib fails to install on osx Status: Invalid Comment #2 on issue 556 by vogt.a...(a)gmail.com: xmonad-contrib fails to install on osx http://code.google.com/p/xmonad/issues/detail?id=556 (No comment was entered for this change.) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 0

Issue 533 in xmonad: clearUrgency should be exported from XMonad.Hooks.UrgencyHook
by codesite-noreply＠google.com 24 Sep '13

24 Sep '13

Status: New Owner: ---- New issue 533 by JohnTy...(a)gmail.com: clearUrgency should be exported from XMonad.Hooks.UrgencyHook http://code.google.com/p/xmonad/issues/detail?id=533 I was trying to make it such that windows which are banished off screen on hidden scratch pad workspaces *never* get urgency set. It was not possible to do so without making my own Urgency Hook, which was fine, except that in order to make it I had no choice but to modify the source and add clearUrgency to the export list. Since "clearUrgents" is exported, which just applies "clearUrgency" to all windows, I don't see why the latter shouldn't also be available. data FilterUrgencyHook = FilterUrgencyHook [String] instance UrgencyHook FilterUrgencyHook where urgencyHook (FilterUrgencyHook skips) w = do ws <- gets windowset case W.findTag w ws of Just tag -> when (tag `elem` skips) (clearUrgency w) _ -> return () -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 8

Re: [xmonad] Issue 551 in xmonad: XMonad.Prompt.Man.manPrompt uses `manpath -g`, -g appears to be an invalid option
by codesite-noreply＠google.com 11 Sep '13

11 Sep '13

Updates: Status: Fixed Comment #4 on issue 551 by vogt.a...(a)gmail.com: XMonad.Prompt.Man.manPrompt uses `manpath -g`, -g appears to be an invalid option http://code.google.com/p/xmonad/issues/detail?id=551 I don't have a system with the other man to test, but it works if one of the two calls to getCommandOutput gives an empty String: Mon Jul 15 23:05:36 EDT 2013 Adam Vogt * Fix issue 551 by also getting manpath without -g flag. Instead of taking Ondrej's approach of figuring out which man (man-db or http://primates.ximian.com/~flucifredi/man/) is used by the system, just try both sets of flags. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 1

Re: [xmonad] Issue 554 in xmonad: mkKeymap (hence additionalKeysP) doesn't handle NLS characters
by codesite-noreply＠google.com 04 Sep '13

04 Sep '13

Comment #2 on issue 554 by byor...(a)gmail.com: mkKeymap (hence additionalKeysP) doesn't handle NLS characters http://code.google.com/p/xmonad/issues/detail?id=554 Hmm, you're right, this ought to be fixed. What's the right way to do it? I am not sure how X11 keysyms are supposed to work. Can they just be arbitrary Unicode codepoints? (I don't even know if that question typechecks.) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 2