From: martin rudalics <rudalics@gmx.at>
To: Richard Copley <rcopley@gmail.com>
Cc: 24500@debbugs.gnu.org
Subject: bug#24500: 25.1.50; Can't other-window from minibuffer if Ediff control panel frame present
Date: Fri, 30 Sep 2016 10:32:46 +0200 [thread overview]
Message-ID: <57EE232E.4090301@gmx.at> (raw)
In-Reply-To: <CAPM58ogQAdzeb=fTGBRW05xP=0w_fhHhgqMsPM9sLp2ESWVYyw@mail.gmail.com>
> With patch (1) the focus can get stuck. Having saved the "my-other-window"
> example above as "x.el", from "emacs -Q",
>
> M-x load-file RET x.el RET ;; Creates and selects a minibuffer-less frame.
> ;; Call the initial frame "frame 1" and the minibuffer-less frame "frame 2".
> C-x b window2 RET ;; Select named window in frame 2 for clarity.
> C-x 5 o ;; Switch to frame 1
> M-x
> C-x 5 o ;; Switch to frame 2
> C-x o ;; Select window *scratch* in frame 1.
> C-x o ;; Select minibuffer.
> C-g ;; Quit M-x
> ;; Selected frame is frame 2
Why do you think so? The selected frame is frame 1 ever since C-x o
selected it (and it did so twice in a row).
> and selected window in frame 2 is "window2",
> ;; but focus is still redirected to frame 1 (selected window now "*scratch*").
> xyzzy ;; Characters are inserted in *scratch*.
>
> No amount of switching between frames 1 and 2 changes the focus
> redirection,
I'm not sure I understand what you mean here. Do you mean that C-x 5 o
after the C-g does not select window2?
> but clicking inside a window on frame 2 does remove
> the redirection and get things back to normal.
What was abnormal before?
> I'll try patch (2) later. It sounds logical to me.
martin
next prev parent reply other threads:[~2016-09-30 8:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 17:23 bug#24500: 25.1.50; Can't other-window from minibuffer if Ediff control panel frame present Richard Copley
2016-09-21 17:47 ` Eli Zaretskii
2016-09-21 20:09 ` Richard Copley
2016-09-22 15:26 ` Eli Zaretskii
2016-09-24 19:04 ` martin rudalics
2016-09-28 23:21 ` Richard Copley
2016-09-30 8:32 ` martin rudalics [this message]
2016-09-30 18:13 ` Richard Copley
2016-09-30 18:21 ` Richard Copley
2016-10-01 8:44 ` martin rudalics
2016-10-01 10:30 ` Richard Copley
2016-10-01 12:29 ` Richard Copley
2016-10-01 13:09 ` martin rudalics
2016-10-01 13:08 ` martin rudalics
2016-10-01 14:54 ` Richard Copley
2016-10-01 18:50 ` martin rudalics
2016-10-03 18:32 ` Richard Copley
2016-10-04 6:49 ` martin rudalics
2016-10-03 19:35 ` Richard Copley
2016-10-04 6:49 ` martin rudalics
2016-10-08 17:37 ` martin rudalics
2016-10-08 18:28 ` Richard Copley
2016-10-09 7:51 ` martin rudalics
2016-10-17 8:58 ` martin rudalics
2016-09-23 6:05 ` Tino Calancha
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=57EE232E.4090301@gmx.at \
--to=rudalics@gmx.at \
--cc=24500@debbugs.gnu.org \
--cc=rcopley@gmail.com \
/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).