From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juri Linkov <juri@linkov.net>
Cc: bugs@gnu.support, 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: Wed, 04 Aug 2021 10:56:53 +0200 [thread overview]
Message-ID: <87lf5hlh9m.fsf@gnus.org> (raw)
In-Reply-To: <87czqtbo47.fsf@mail.linkov.net> (Juri Linkov's message of "Wed, 04 Aug 2021 11:39:04 +0300")
Juri Linkov <juri@linkov.net> writes:
>>> + ;; When read_minibuf doesn't restore all previous windows,
>>> + ;; then at least pop down the completions window.
>>> + (unless read-minibuffer-restore-windows
>>> + (minibuffer-hide-completions))
>>
>> Hm... Well, I guess that's what most people would want... but...
>
> The new option read-minibuffer-restore-windows is quite unusable
> without the above change: selecting a completion from the
> completions buffer will leave the completions buffer on the screen.
Yes. But I think some people would want that -- that is, they might be
`C-g'-ing out of the minubuffer just because they want to copy some of
the text in the completions buffer.
But on the other hand, that may be such a rare thing to do that just
applying your proposed patch is the right thing, and then we could just
see whether anybody actually requests that before tinkering any further
with it...
So... I think you should just push the patch, and then we'll see.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-08-04 8:56 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
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 [this message]
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=87lf5hlh9m.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=45072@debbugs.gnu.org \
--cc=bugs@gnu.support \
--cc=juri@linkov.net \
/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).