KRunner behavior change

[Matej Svejda]

BTW: Is deactivating m_execQueued (setting it to false) at the end if
Interface::updateMatches intentional? It a) doesn't make any sense and
b) if you comment this out it solves one problem that has been bugging
me about KRunner:
When you _know_ that what you typed will result in the right match
(e.g. you typed konq for konqueror) but you are too fast in pressing
return your input is ignored. When you remove that line of code
(m_execQueued = false) this behavior goes away. I guess that's what
m_execQueued was meant to fix, isn't it?

Matej