From: Eli Zaretskii <eliz@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: larsi@gnus.org, 45072@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: Mon, 07 Dec 2020 19:20:08 +0200 [thread overview]
Message-ID: <83eek18ref.fsf@gnu.org> (raw)
In-Reply-To: <X85bhc/D4Xsat7Vv@protected.rcdrun.com> (message from Jean Louis on Mon, 7 Dec 2020 19:42:45 +0300)
> Date: Mon, 7 Dec 2020 19:42:45 +0300
> From: Jean Louis <bugs@gnu.support>
> Cc: 45072@debbugs.gnu.org
>
> Why is that default there?
Because minibuffer input can easily create one or more additional
windows, e.g. to show the completion candidates, and we don't want
that to be left on display when you exit the minibuffer.
My recommendation is not to "abuse" the recursive editing; the ELisp
manual rightfully warns against that, albeit indirectly. If you
frequently need ti switch away of the minibuffer without exiting it, I
suggest to use a separate frame for your excursions: when exiting the
minibuffer, Emacs only restores the windows on the frame where you
entered the minibuffer (assuming you aren't using minibuffer-only
frames).
next prev parent reply other threads:[~2020-12-07 17:20 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 14:07 bug#45072: 28.0.50; Emacs switches other buffer back uncontrollably, if other window's buffer is changed by user during minibuffer editing Jean Louis
2020-12-07 16:10 ` Lars Ingebrigtsen
2020-12-07 16:42 ` Jean Louis
2020-12-07 17:20 ` Eli Zaretskii [this message]
2020-12-07 18:49 ` Jean Louis
2020-12-07 19:27 ` Eli Zaretskii
2020-12-07 19:45 ` Jean Louis
2020-12-08 8:09 ` martin rudalics
2020-12-08 14:09 ` Lars Ingebrigtsen
2020-12-08 14:18 ` Jean Louis
2020-12-08 14:47 ` martin rudalics
2020-12-08 14:58 ` Jean Louis
2020-12-08 16:08 ` Eli Zaretskii
2020-12-08 16:14 ` Jean Louis
2020-12-08 15:51 ` Eli Zaretskii
2020-12-09 9:33 ` martin rudalics
2021-08-03 7:57 ` Juri Linkov
2021-08-04 6:52 ` Lars Ingebrigtsen
2021-08-04 8:39 ` Juri Linkov
2021-08-04 8:56 ` Lars Ingebrigtsen
2021-08-04 20:17 ` Juri Linkov
2021-08-05 10:55 ` Lars Ingebrigtsen
2021-08-05 23:36 ` Juri Linkov
2020-12-08 19:15 ` Juri Linkov
2020-12-09 9:34 ` martin rudalics
2020-12-09 10:06 ` Jean Louis
2020-12-09 15:16 ` martin rudalics
2020-12-09 19:11 ` Juri Linkov
2020-12-10 7:44 ` martin rudalics
2020-12-10 8:30 ` Jean Louis
2020-12-10 9:46 ` martin rudalics
2020-12-10 10:16 ` Jean Louis
2020-12-10 11:52 ` martin rudalics
2020-12-10 12:07 ` Jean Louis
2020-12-11 9:39 ` Juri Linkov
2020-12-12 1:47 ` Jean Louis
2020-12-10 8:32 ` Juri Linkov
2020-12-10 9:47 ` martin rudalics
2020-12-10 10:21 ` Jean Louis
2020-12-10 11:52 ` martin rudalics
2020-12-10 12:21 ` Jean Louis
2020-12-12 20:49 ` Juri Linkov
2020-12-13 7:26 ` martin rudalics
2020-12-14 20:28 ` Juri Linkov
2020-12-15 7:59 ` martin rudalics
2021-01-15 8:57 ` Juri Linkov
2021-04-19 13:54 ` Stefan Monnier
2021-04-19 16:02 ` martin rudalics
2021-04-19 18:09 ` Juri Linkov
2021-04-19 13:52 ` Stefan Monnier
2021-04-19 16:02 ` martin rudalics
2021-04-19 16:22 ` Stefan Monnier
2021-04-19 17:11 ` martin rudalics
2020-12-08 5:33 ` Richard Stallman
2020-12-08 15:13 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83eek18ref.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45072@debbugs.gnu.org \
--cc=bugs@gnu.support \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).