[xmonad] Revisiting XMonad.Prompt
nwfilardo at gmail.com
Wed Nov 16 17:22:10 CET 2011
Well, I took a stab at it, but it's broken. :( If somebody could look
at http://www.acm.jhu.edu/~nwf/prompt-core.dpatch (the (small) set of
changes needed to xmonad core) and
http://www.acm.jhu.edu/~nwf/prompt-contrib.dpatch, I'd be grateful.
Note that to run the code, you'll have to add
XMonad.Prompt.eventHandle to your eventHook in xmonad's configuration
and that I haven't patched xmonad-extras yet.
On Tue, Nov 15, 2011 at 3:22 PM, Nathaniel Filardo <nwfilardo at gmail.com> wrote:
> 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.
> Thanks in advance.
More information about the xmonad