From: Eli Zaretskii <eliz@gnu.org>
To: 41338@debbugs.gnu.org, stephen.berman@gmx.net, rudalics@gmx.at
Cc: konrad.podczeck@univie.ac.at, juri@linkov.net
Subject: bug#41338: Toolbar-bug in Emacs 27.0.91/Pretest
Date: Sun, 17 May 2020 15:36:10 +0300 [thread overview]
Message-ID: <F8F75713-04BE-48F0-B2A8-83028474DD1E@gnu.org> (raw)
In-Reply-To: <874ksfexjr.fsf@gmx.net>
On May 17, 2020 12:11:04 PM GMT+03:00, Stephen Berman <stephen.berman@gmx.net> wrote:
> On Sun, 17 May 2020 10:56:50 +0200 Stephen Berman
> <stephen.berman@gmx.net> wrote:
>
> > On Sun, 17 May 2020 10:20:55 +0200 martin rudalics <rudalics@gmx.at>
> wrote:
> >
> >>> But I don't know why the ‘delete-frame’ event is not fired on
> frame deletion.
> >>
> >> How do you delete the frame? You don't get a 'delete-frame' event
> when
> >> you delete a frame via C-x 5 0 or C-x 5 1.
> >>
> >> martin
> >
> > In my test I followed the OP's recipe:
> >
> >> (7) Using the mouse, close the frame showing mouse.el, but do so in
> a state
> >> where still isearch overlays show up.
> >
> > I.e., I clicked on the 'X' (close frame button) in the frame's title
> > bar.
>
> But when I close the frame with `C-x 5 0' instead and then proceed
> with
> the OP's recipe, the tool bar does not change and when I switch to the
> buffer where isearch had been invoked, the search is now abandoned,
> i.e., no isearch tool bar or lighter, no overlays. So only closing
> the
> frame by clicking the close frame button with the mouse induces the
> surprising behavior.
>
> Steve Berman
Could someone please explain to me what is deemed to be the bug here? Because I'm confused wrt what is the part of the original description that seems to be the problem. In particular, the Isearch overlays are per-window, AFAIK.
next prev parent reply other threads:[~2020-05-17 12:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 20:43 bug#41338: Toolbar-bug in Emacs 27.0.91/Pretest Konrad Podczeck
2020-05-16 21:34 ` Stephen Berman
2020-05-16 22:55 ` Juri Linkov
2020-05-17 8:20 ` martin rudalics
2020-05-17 8:56 ` Stephen Berman
2020-05-17 9:11 ` Stephen Berman
2020-05-17 12:36 ` Eli Zaretskii [this message]
2020-05-17 12:59 ` Stephen Berman
2020-05-17 13:12 ` Eli Zaretskii
2020-05-17 13:37 ` Stephen Berman
2020-05-17 14:22 ` Eli Zaretskii
2020-05-17 14:49 ` Stephen Berman
2020-05-17 22:03 ` Juri Linkov
2020-05-17 22:04 ` Juri Linkov
2020-05-18 16:25 ` Drew Adams
2020-05-19 22:01 ` Juri Linkov
2020-06-11 22:51 ` Juri Linkov
2020-06-13 22:56 ` Juri Linkov
2020-06-14 22:55 ` Juri Linkov
2023-03-09 17:14 ` Juri Linkov
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=F8F75713-04BE-48F0-B2A8-83028474DD1E@gnu.org \
--to=eliz@gnu.org \
--cc=41338@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=konrad.podczeck@univie.ac.at \
--cc=rudalics@gmx.at \
--cc=stephen.berman@gmx.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).