From: martin rudalics <rudalics@gmx.at>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 24803@debbugs.gnu.org
Subject: bug#24803: Redirection problem with separate minibuffer frame
Date: Sun, 30 Oct 2016 09:47:17 +0100 [thread overview]
Message-ID: <5815B395.9030905@gmx.at> (raw)
In-Reply-To: <jwv7f8q6agf.fsf-monnier+emacsbugs@gnu.org>
> Reverting the frame.c change seems to fix the problem.
As expected. Please keep it this way for the moment. If we don't find
a better solution, I'll do the revert on master. Currently, I'd be more
interested if someone else sees the same or a similar problem.
> BTW I also just noticed that the bogus (the one I get at the end of my
> recipe) focus is "mutual":
> - when the mouse points at the minibuffer window, the focus is in the
> *scratch* buffer.
> - when the mouse points in the *scratch* window, the focus is in the
> minibuffer!
With emacs -Q and just ‘display-buffer-alist’ customized and no
minibuffer dialogue in process? Queer.
>> Hmm... This seems to indicate that I do not remove the redirection when
>> exiting the minibuffer. Could you try to augment in read_minibuf_unwind
>>
>> if (minibuf_level == 0)
>> resize_mini_window (XWINDOW (window), 0);
>>
>> to something that for each frame redirects focus to itself?
>
> Still haven't found the time to try this, but I just want to mention
> that until recently, the focus redirection was usually nil rather than
> "redirected to itself".
Indeed you would have to set it to nil. And obviously my proposal is
not a solution anyway since someone might want to redirect focus without
any minibuffers being involved in the first place.
> I'm not sure if there should be a difference between these two states,
> but I have the suspicion that not all the C code handles those two
> states in the same way (then again, last time I looked at the
> redirection code, I concluded that I just don't understand how it's
> supposed to work, so maybe it's just my misunderstanding).
I'm currently struggling with focus redirection in various contexts -
for example, when redirecting focus from a parent to a child frame and
back again. So far it's a lost battle :-(
martin
next prev parent reply other threads:[~2016-10-30 8:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 18:09 bug#24803: Redirection problem with separate minibuffer frame Stefan Monnier
2016-10-27 17:35 ` martin rudalics
2016-10-29 22:54 ` Stefan Monnier
2016-10-30 8:47 ` martin rudalics [this message]
2020-11-25 9:26 ` martin rudalics
2021-05-19 8:12 ` martin rudalics
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=5815B395.9030905@gmx.at \
--to=rudalics@gmx.at \
--cc=24803@debbugs.gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).