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: Sat, 01 Oct 2016 15:09:04 +0200 [thread overview]
Message-ID: <57EFB570.7010409@gmx.at> (raw)
In-Reply-To: <CAPM58ojxBGBQ4naDAmJmSqUaxHSy_-_WxMX5y_gzDdBdbjgYRg@mail.gmail.com>
> At this point the video begins.
>
> ;; Click inside *scratch* in the left frame.
> M-x
> ;; Click the title bar of the Right Window.
> C-x o ;; Select window *scratch* in frame 1.
> C-x o ;; Select minibuffer.
> C-g ;; Quit M-x
So far we've been talking about what happens when you hit C-x o and C-g
has not been reached yet. Obviously C-g cancels the entire minibuffer
indirection setup and from then on C-x o will continue to stay within
the frame where it was typed. This is the standard behavior and I
obviously get the same as you until here.
> xxx ;; Characters inserted in *scratch*
> ;; Click on the title bar on the left.
> xxx ;; Characters inserted in *scratch*
> ;; Click on the title bar on the right.
> xxx ;; Characters inserted in *scratch*
> ;; Click inside window2 on the right.
> xxx ;; Characters inserted in window2.
This is abnormal indeed and I can't observe that here. Whenever I click
on a title bar or within a window, the associated fame gets selected and
input focus and all typed text goes there.
martin
next prev parent reply other threads:[~2016-10-01 13:09 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
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 [this message]
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=57EFB570.7010409@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).