bug#9972: 24.0.90; "C-s/C-r" from the minibuffer don't clear the current text

[Dani Moncayo <dmoncayo@gmail.com>]

On Sun, Nov 6, 2011 at 17:16, Juri Linkov <juri@jurta.org> wrote:
>> IMO, It isn't worth making C-s (and C-r, C-M-s, C-M-r) look up also in
>> the current minibuffer text, because it is usually small enough not to
>> need that (how often do you use that feature?).
>
> I use this feature all the time!

For searching in the _current_ minibuffer text?  How long are such text?

>> I'd like these commands (C-s, C-r, C-M-s, C-M-r) to be similar to M-s and M-r:
>> * Focus exclusively in the minibuffer history.
>> * Have a minibuffer-specific prompt ("Next/Previous element matching
>> [regexp]: ") so that it is clear what's going on.
>> * Obviously, clear the minibuffer's current input.
>
> If you like M-s and M-r, then just use them.  They are like non-incremental
> versions `M-x search-forward RET' and `M-x search-backward RET'.

I can use them, of course, but as you've said, they are not
incremental.  Precisely, as I pointed out, I'd like to adjust C-M-s to
be the incremental version of M-s.

> But C-s should work like Isearch, and not clear text before it starts to
> search in it.

Well, think of the advantages and drawbacks.  IMHO, my proposal would
make the Isearch commands (in the minibuffer):
* More useful: what you want is to go straight to the history.
* Clearer: The prompt states clearly that you are searching the in
history, and nowhere else.
* Consistent with M-s and M-r.

-- 
Dani Moncayo