From: Stephen Berman <stephen.berman@gmx.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 48258@debbugs.gnu.org
Subject: bug#48258: 28.0.50; minibuffer window not selected with non-nil mouse-autoselect-window
Date: Fri, 01 Jul 2022 14:43:30 +0200 [thread overview]
Message-ID: <8735fl57gt.fsf@gmx.net> (raw)
In-Reply-To: <87h74158s3.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 01 Jul 2022 14:15:08 +0200")
On Fri, 01 Jul 2022 14:15:08 +0200 Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Stephen Berman <stephen.berman@gmx.net> writes:
>
>> 0. emacs -Q
>> 1. Type `M-x set-variable mouse-autoselect-window RET t RET'.
>> 2. Type `M-x gnus', answer `y' at the prompt; in the Gnus buffer type
>> `B RET news.gmane.io RET'.
>> 3. In the *Gnus Browse Server* buffer type `C-s gmane.emacs.devel' to
>> put point on the gmane.emacs.devel group; type RET to enter it.
>> 4. Type `j <b83ee8b3-0889-0796-e5f0-f18fcb8701b4@icloud.com> RET', which
>> displays an article containing an attachment.
>> 5. Type `2 K o'.
>> => The minibuffer displays a prompt to enter where to save the MIME part
>> to, but the selected window remains the one containing Gnus Summary
>> buffer instead of switching to the minibuffer window (but see below).
>
> [...]
>
>> Sometimes there is no failure to select the minibuffer window the first
>> time around, but I haven't been able to isolate the necessary
>> conditions.
>
> (I'm going through old bug reports that unfortunately weren't resolved
> at the time.)
>
> I'm unable to reproduce this in Emacs 29. Do you still see this
> behaviour in the current Emacs?
No, and I can't reproduce it now on Emacs 27 and 28 either, so I guess
the bug should be closed as unreproducible.
Steve Berman
next prev parent reply other threads:[~2022-07-01 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 15:41 bug#48258: 28.0.50; minibuffer window not selected with non-nil mouse-autoselect-window Stephen Berman
2022-07-01 12:15 ` Lars Ingebrigtsen
2022-07-01 12:43 ` Stephen Berman [this message]
2022-07-01 12:49 ` Lars Ingebrigtsen
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=8735fl57gt.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=48258@debbugs.gnu.org \
--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).