- xmonad - Haskell.org

darcs patch: ShellPrompt.hs: a quick optimization of nub
by gwern0＠gmail.com 16 Oct '07

16 Oct '07

Mon Oct 15 19:48:50 EDT 2007 gwern0(a)gmail.com * ShellPrompt.hs: a quick optimization of nub I saw some complaints about ShellPrompt being slow - and noticed it myself - and it seems ShellPrompt uses 'nub' in an awkward place to uniquefy input. Nub doesn't perform well on long lists, but I once ran into a similar problem and the suggested solution was something clever: convert to a Set and then back to a List. Sets can't have duplicate entries, and they uniquefy faster than nub. The price is that the output is not sorted the same as nub's output would be, but this is OK because the output of (toList . fromList) is immediately passed to 'sort' - which should then produce the same output for both versions. I haven't really tested this but on long directories this should help.

4 3

Re: [Xmonad] dynamic workspaces, session restore
by Valery V. Vorotyntsev 16 Oct '07

16 Oct '07

On 10/16/07, Daniel Spoonhower <spoons+(a)cs.cmu.edu> wrote: > > > 3) Can I define a key binding like, say, `Win-k 1'? > > > > The pattern is `<modifiers>-<key1> <key2>'. I find such > > screen/ion/emacs-y keystrokes very handy. :) > > > > Yes, see XMonadContrib/Submap.hs > > For example, as a single item in the "keys" map you might have: > > -- less frequently used actions > , ((modMask, xK_k), submap . M.fromList $ > [ ((0, xK_c), kill) -- @@ Close window > , ((0, xK_period), sendMessage (IncMasterN 1)) > , ((0, xK_comma), sendMessage (IncMasterN (-1))) > , ((modMask, xK_space ), setLayout defaultLayout) > , ((0, xK_Return), withFocused $ windows . W.sink) > ] Great! Thank you. :)

1 0

Issue 61 in xmonad: XPrompt Ctrl+keys don't work with NumLock
by codesite-noreply＠google.com 15 Oct '07

15 Oct '07

Issue 61: XPrompt Ctrl+keys don't work with NumLock http://code.google.com/p/xmonad/issues/detail?id=61 Comment #1 by lit...(a)hethrael.com: CapsLock causes the same problem. -- 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 61 in xmonad: XPrompt Ctrl+keys don't work with NumLock
by codesite-noreply＠google.com 15 Oct '07

15 Oct '07

Issue 61: XPrompt Ctrl+keys don't work with NumLock http://code.google.com/p/xmonad/issues/detail?id=61 New issue report by lit...(a)hethrael.com: What steps will reproduce the problem? 1. Turn NumLock on. 2. Pop up an XPrompt. 3. Type something. 4. Press Ctrl+U. What is the expected output? What do you see instead? All text before the cursor should be erased. Instead, a box glyph appears. What version of the product are you using? On what operating system? Current darcs. If this error is due to a module from XMonadContrib, please tag this issue with 'Component-Contrib' below. How? Issue attributes: Status: New Owner: ---- Labels: Type-Defect Priority-Medium -- 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: fix float bug in CopyWindow.
by David Roundy 15 Oct '07

15 Oct '07

Mon Oct 15 12:15:29 EDT 2007 David Roundy <droundy(a)darcs.net> * fix float bug in CopyWindow.

1 0

darcs patch: improvements in Combo.
by David Roundy 15 Oct '07

15 Oct '07

Mon Oct 15 09:28:39 EDT 2007 David Roundy <droundy(a)darcs.net> * improvements in Combo.

1 0

darcs patch: WindowNavigation: don't export the config constructor ...
by Andrea Rossato 15 Oct '07

15 Oct '07

this is not just haddock, even though there are no added functionality. It is just something I promise david I would have taken care of but I had no time to. Apply at your discretion. Andrea Sat Oct 13 11:05:24 CEST 2007 Andrea Rossato <andrea.rossato(a)unibz.it> * WindowNavigation: don't export the config constructor and some haddock fixes I told to David I would have taken care of that: instead of exporting the config constructor we export 2 functions: navigateColor and noNavigateBorders. Updated documentation accordingly.

3 3

Issue 60 in xmonad: XPrompt uses 100% CPU while displayed
by codesite-noreply＠google.com 14 Oct '07

14 Oct '07

Issue 60: XPrompt uses 100% CPU while displayed http://code.google.com/p/xmonad/issues/detail?id=60 Comment #3 by SpencerJanssen: I've tripped on this bug before, quite frustrating. Marked as 'Invalid' since it is a bug in Xlib, not xmonad. Issue attribute updates: Status: Invalid -- 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 60 in xmonad: XPrompt uses 100% CPU while displayed
by codesite-noreply＠google.com 14 Oct '07

14 Oct '07

Issue 60: XPrompt uses 100% CPU while displayed http://code.google.com/p/xmonad/issues/detail?id=60 Comment #2 by james.w...(a)sygneca.com: Yes, you are quite right. Upgrading to 1.1.2 fixed it. 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

1 0

Issue 60 in xmonad: XPrompt uses 100% CPU while displayed
by codesite-noreply＠google.com 14 Oct '07

14 Oct '07

Issue 60: XPrompt uses 100% CPU while displayed http://code.google.com/p/xmonad/issues/detail?id=60 Comment #1 by andrea.rossato: I think you are experiencing a Xlib bug that I believe was corrected in version 1.1.2. Xlib 1.1.1 is still affected, while 1.1.3 is not (I tried personally). Which version are you using? If you cannot upgrade Xlib I can suggest a (not nice) work around. Edit XmonadContrib.XPrompt and change (in line 204): maskEvent d (exposureMask .|. keyPressMask) e to nextEvent d e Hope this helps, Andrea -- 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