GNU bug report logs - #45072
28.0.50; Emacs switches other buffer back uncontrollably, if other window's buffer is changed by user during minibuffer editing

Previous Next

Full log

View this message in rfc822 format

From: Jean Louis <bugs <at> gnu.support>
To: martin rudalics <rudalics <at> gmx.at>
Cc: Lars Ingebrigtsen <larsi <at> gnus.org>, Eli Zaretskii <eliz <at> gnu.org>, 45072 <at> debbugs.gnu.org
Subject: bug#45072: 28.0.50; Emacs switches other buffer back uncontrollably, if other window's buffer is changed by user during minibuffer editing
Date: Tue, 8 Dec 2020 17:58:40 +0300

* martin rudalics <rudalics <at> gmx.at> [2020-12-08 17:47]:
> > Looks good to me, but I'd revert the logic, as "negative" variables have
> > a tendency to be misunderstood.  That is, call the variable
> > `read-from-minibuffer-restore' and default it to t instead.
> 
> Coming from the frame/window department I'm usually against defaulting
> options to non-nil because nil-valued and absent parameters behave the
> same way.  But I have no problems doing what you propose.  Let's see if
> anyone really wants such an option.

I would prefer by default not to switch windows for me as if I am user
and switched the other buffer why would I need it automatically back?
I switched it because I do not need it.

Please understand how it is to work in a loop in minibuffer, many
coordinates have to be entered carefully and various maps consulted,
and then even though buffers were switched there and back on each new
invocation of minibuffer prompt all those buffers go away.

From the view point of having user control, I would rather have that
option turned off by default.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.