In normal isearch operation (i.e. not in the minibuffer), typing C-s
immediately moves point to the next occurrence of the search string
and highlights it.
Having a delay in the minibuffer between typing C-s and seeing the search
string highlighted, or requiring to type another
> The delay is 2 sec, and it is caused by sit-for in minibuffer-message.
>
> sit-for is supposed exit whenever you type another character.
> So in what sense does it cause a "delay"?
In normal isearch operation (i.e. not in the minibuffer), typing C-s
immediately moves point to the next occurr
> This doesn't work satisfactorily: temporarily displaying the search
> prompt at the end of the minibuffer causes too long delay after typing
> C-s and before point moves to the next occurrence of the search
string.
>
> Could you be more specific? How long is the
the delay, and what causes it?
The delay is 2 sec, and it is caused by sit-for in minibuffer-message.
> 1. not to display the search prompt while searching in the minibuffer
> at all, because the search string is highlighted in the minibuffer anyway.
> Thus the search prompt wi
es it?
1. not to display the search prompt while searching in the minibuffer
at all, because the search string is highlighted in the minibuffer anyway.
Thus the search prompt will not obscure the minibuffer text, and users
will be provided with visual feedback about the place the s
out.
This doesn't work satisfactorily: temporarily displaying the search
prompt at the end of the minibuffer causes too long delay after typing
C-s and before point moves to the next occurrence of the search string.
Instead of that, I propose a different solution:
1. not to display t
