RE: [External] : Re: Simple isearch concerns

[Drew Adams <drew.adams@oracle.com>]

Apologies for not following this thread.  It seems to be
quite wide in its scope (but I could easily just be
misunderstanding).

Is there really a focus on somehow changing just `M-e'
(edit the search pattern, with searching suspended while
doing that)?  Somehow I've gotten the impression that
much more seems to be under discussion (i.e., at stake).

What really is the _concrete problem_ that you're trying
to solve, for which you think (IIUC) that Isearch should
use the minibuffer (aside from the current uses it makes
of the minibuffer, which are really outside searching)?

Somehow, this kinda feels like an X-Y problem.

https://meta.stackexchange.com/questions/66377/what-is-the-xy-problem

And the OP seems to say (again, IIUC) that though he's
used Isearch for years he's never really understood the
C-g behavior (and DEL perhaps).  Is there an Isearch
problem or a learning/doc problem?
___

Those are just comments/questions from impressions I've
had while perusing some of the posts in the thread.
They might reflect gross misunderstanding (or rather,
lack of understanding) of what the problem and the
proposed solution really are.

Here, at least, is a concrete question:

If the minibuffer becomes the buffer that will be current
when using Isearch (I thought I saw that as a proposal),
will it still be possible to use Isearch in the minibuffer,
i.e., to search text in the minibuffer, when the minibuffer
is being used normally (not by Isearch)?

That's important, IMO: being able to use Isearch in any
minibuffer, to search its text.