From: Richard Copley <rcopley@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 24500@debbugs.gnu.org
Subject: bug#24500: 25.1.50; Can't other-window from minibuffer if Ediff control panel frame present
Date: Mon, 3 Oct 2016 20:35:38 +0100 [thread overview]
Message-ID: <CAPM58ojQUSijjgqMWtyJKLDH2aGNvq-PSTZtcLH8CiTeUm+qcQ@mail.gmail.com> (raw)
In-Reply-To: <CAPM58ogQAdzeb=fTGBRW05xP=0w_fhHhgqMsPM9sLp2ESWVYyw@mail.gmail.com>
On 29 September 2016 at 00:21, Richard Copley <rcopley@gmail.com> wrote:
> On 24 September 2016 at 20:04, martin rudalics <rudalics@gmx.at> wrote:
>> I attached two patches that seem to work, but without any warranty (I do
>> not fully understand the intentions of frame-focus/focus_frame and
>> x_get_focus_frame yet). The purpose of these patches is to keep the
>> ‘next-window’ and ‘other-window’ mechanisms symmetric whenever a frame
>> shares its minibuffer with other frames:
>>
>> (1) The frame.c patch changes the behavior of ‘do_switch_frame’ by
>> redirecting focus to another frame that shares this frame's minibuffer
>> even when that other frame has no pending minibuffer activity.
>>
>> (2) The window.c patch simply inhibits ‘next-window’ to select a window
>> on a frame that has no pending minibuffer activity.
>>
>> Please try these patches (only one at a time because the window.c patch
>> makes the frame.c patch moot) and tell me whether they have any bad
>> effects.
>>
>> Thanks, martin
>
> Thank you!
>
[...]
>
> I'll try patch (2) later. It sounds logical to me.
I've been using the window.c patch for a few days and I haven't noticed
any badness.
next prev parent reply other threads:[~2016-10-03 19:35 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPM58ojQUSijjgqMWtyJKLDH2aGNvq-PSTZtcLH8CiTeUm+qcQ@mail.gmail.com \
--to=rcopley@gmail.com \
--cc=24500@debbugs.gnu.org \
--cc=rudalics@gmx.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.