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

[Dani Moncayo <dmoncayo@gmail.com>]

>>>> 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?
>
> It doesn't matter how long it is.
>
> Just imagine the minibuffer search as continuously searching backward
> in a buffer with lines:
>
> history3
> history2
> history1
> history0
>
> where "history0" is initial text in the minibuffer.
>
> What you propose is to delete the line "history0" before running Isearch.
> This makes no sense at all.

Like you (and Drew, and I guess everyone in this list), I like
consistency and generality.

Actually, what I don't like in the current behavior of C-s (and the
other 3) when invoked from the minibuffer is the fact that the current
minibuffer text remains there after hitting C-s (like if I were typed
it, but even being read-only!).  That scenario is not like users are
used to when the type `C-s'.  They expect to see a clean minibuffer
prompt "I-search: ", with the cursor after it.

So, what about making the Isearch commands start that way, but
considering the current minibuffer text (the one present before C-s
was invoked) as the first entry for the search, as you pointed out?



-- 
Dani Moncayo