On Tue, Nov 15, 2011 at 3:22 PM, Nathaniel Filardo
I have wanted, for a long while, to revisit XMonad.Prompt and make it use the main event hook, rather than its own sneaky manipulation down in IO land. I've started working on it as I consider the current behavior a bit of a wart, but it will mean the loss of mkXPromptWithReturn and the making-asynchronous of mkXPrompt. (i.e. The String -> X () argument will be invoked after the function has returned.) In looking through XMonadContrib, it looks like most users of XMonad.Prompt would be OK with this; xmonad-extras' XMonad.Prompt.Eval and XMonad.Prompt.MPD would need to be rewritten (which I can do, I think) and so I wonder if other users would notice the shift? If there's not overwhelming objection, I'll get a patch out soon for people to review.
Looking through the config archive, I don't see any users of that function. So as long as you don't break anything in XMC you don't fix, there probably wouldn't be any problems. Aside from that, I conclude that XMonad 1.0 must be released. -- gwern http://www.gwern.net