Re: read-char-from-minibuffer ends keyboard macro recording

[Juri Linkov]

> Hi, there's a problem with recent changes to read-char-from-minibuffer
> (commit 04ab67470706f1c66bdf08e4078ea3dffd79b41e): this function invokes
> (discard-input) at the very beginning, thus making it impossible to use
> it as part of the keyboard macro (through zap-to-char or otherwise).

'(discard-input)' was added to swallow some initial events.
Without it, 'sit-for' in 'minibuffer-message' doesn't wait
2 seconds to display the message.  Such events occur only
at Emacs startup, and they need to be discarded to display
the message for 2 seconds when the minibuffer is activated
to ask a question about loading the desktop or visiting
a file with local variables loaded from the desktop.

We need first to solve the problem with initial events
before removing '(discard-input)'.