unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Konrad Podczeck <konrad.podczeck@univie.ac.at>
Cc: 41338@debbugs.gnu.org
Subject: bug#41338: Toolbar-bug in Emacs 27.0.91/Pretest
Date: Sat, 16 May 2020 23:34:36 +0200	[thread overview]
Message-ID: <87ftbzva1f.fsf@rub.de> (raw)
In-Reply-To: <A68C1CC2-966B-482F-AF0D-4BDFC1B3A898@univie.ac.at> (Konrad Podczeck's message of "Sat, 16 May 2020 22:43:25 +0200")

On Sat, 16 May 2020 22:43:25 +0200 Konrad Podczeck <konrad.podczeck@univie.ac.at> wrote:

> To reproduce:
>
> (1) Start Emacs (without any customizations).
>
> (2) Open a file which has the standard toolbar, say mouse.el
>
> (3) Do C-x m, to open a message buffer; this buffer has a toolbar _different_
> from the standard one.
>
> (4) Do C-x 5 2, to get the message buffer shown in a second frame.
>
> (5) In the first frame, make the buffer showing mouse.el active again.
>
> (6) In that buffer, do C-s, to invoke isearch and search for some word.
>
> (7) Using the mouse, close the frame showing mouse.el, but do so in a state
> where still isearch overlays show up.
>
> (8) Now click with mouse-1 in the remaining frame, i.e., in that showing the
> message buffer, and the toolbar changes to the standard one.
>
> I consider this as a bug. In case it is not platform independent, I us an NS-build.

I see this too, on GNU/Linux (both in 27.0.91 and a recent build from
master).  Moreover, if in the remaining frame I switch from the message
buffer to the buffer in which isearch was invoked, the tool bar is now
the isearch tool bar and the mode line has the "Isearch" lighter, but
there are no isearch overlays and point is where it was before invoking
isearch.  This seems surprising.  But now typing C-s restores the
isearch state the buffer had (i.e. the same overlays) before closing the
other frame.

Steve Berman





  reply	other threads:[~2020-05-16 21:34 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 [this message]
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
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=87ftbzva1f.fsf@rub.de \
    --to=stephen.berman@gmx.net \
    --cc=41338@debbugs.gnu.org \
    --cc=konrad.podczeck@univie.ac.at \
    /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).