bug#45617: <query-replace> loses the edit region. Works in 23.3, broke in 26.3

["Bob Floyd" <bobfloyd@comcast.net>]

Perhaps another way to think about this is that emacs is "mode-less".

I can begin a command, recurse into another, pop out and resume the first
command.

Without the patch, or minibuffer fix, <query-replace> breaks that design.

If the minibffer fix better supports mode-less operation in general it would
be better than the patch.

-----Original Message-----
From: Eli Zaretskii [mailto:eliz@gnu.org] 
Sent: Wednesday, January 6, 2021 10:19 AM
To: Juri Linkov
Cc: bobfloyd@comcast.net; 45617@debbugs.gnu.org
Subject: Re: bug#45617: <query-replace> loses the edit region. Works in
23.3, broke in 26.3

> From: Juri Linkov <juri@linkov.net>
> Cc: "'Eli Zaretskii'" <eliz@gnu.org>,  <45617@debbugs.gnu.org>
> Date: Wed, 06 Jan 2021 19:44:30 +0200
> 
> > For my two cents, what you write sounds like the real problem is the
> > minibuffer failing to restore on exit. A fix to that would be preferable
to
> > the patch. After all, who knows what else may affected by the
minibuffer!
> > I'd be happy to test this alternative.
> 
> The question we need to answer: should this fix affect all other uses
> of the minibuffer?  So for any command that operates on the active region
> and asks its arguments from the minibuffer, when you copy the text
> from the original buffer to the minibuffer and thus change its region,
> should quitting the minibuffer restore the original region for
> all such commands?  This means restoring the original mark and point.

I think the answer is YES, especially if we did behave like that in
the distant past.