Need to type keybindings twice after startup for effect

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start xmonad
2. Type a keybinding (say mod-shift-return)
3. Observe that nothing happens
4. Type it again
5. Observe that the terminal is started

First I believed it had something to do with xmobar which I'm using:
http://www.haskell.org/pipermail/xmonad/2008-March/005060.html

But that doesn't seem to be the problem.

What version of the product are you using? On what operating system?
Latest version from darcs 13 march 2008

Please provide any additional information below.
I attached my ~/.xmonad/xmonad.hs and ~/.xsession for reference.

Original issue reported on code.google.com by v.dijk....@gmail.com on 13 Mar 2008 at 11:48

Attachments:

• .xsession
• xmonad.hs

[GoogleCodeExporter]

This may seem silly, but I'd just like to make sure: have you given xmonad 
enough
time to initialize and begin listening for keypresses before typing them?  If 
the
cached xmonad binary is stale compared to your xmonad.hs, this may take a 
significant
amount of time.

Perhaps another program is stealing this first keypress?  I'm not familiar 
enough
with the programs in your .xsession to know whether this is the case.

Original comment by SpencerJ...@gmail.com on 16 Mar 2008 at 7:39

[GoogleCodeExporter]

I think this is almost certainly the delay. I've been unable to reproduce it.

Original comment by don...@gmail.com on 26 Mar 2008 at 1:16

[GoogleCodeExporter]

Original comment by SpencerJ...@gmail.com on 26 Mar 2008 at 2:51

• Changed state: Invalid