From: Robert Weiner <rsw@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: select-frame-set-input-focus fails to raise the frame
Date: Wed, 13 Dec 2017 10:00:50 -0500 [thread overview]
Message-ID: <CA+OMD9h8EHvDBV-w_sXBu-Oy_nco7LVJN2_3R+gsOiuD_dtaeg@mail.gmail.com> (raw)
In-Reply-To: <5A30E9E2.5060504@gmx.at>
[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]
On Wed, Dec 13, 2017 at 3:50 AM, martin rudalics <rudalics@gmx.at> wrote:
> > Is there something wrong in the test function or is there a problem in
> > select-frame-set-input-focus?
>
> Even if you get a thing like this work on your system, there will be
> always another platform where it fails.
Can you explain what the problem is and why you think it is unsolvable?
In the prior example with raise-frame and lower-frame, we see there is
no problem combining the two of these but once (next-frame) is added
the combination of the two does not work. Why? Why would you expect
that to be the case? Why is it not a bug?
Note the remark in xfns.c:
>
> In an ideal world, XSetInputFocus should generally be avoided so
> that applications don't interfere with the window manager's focus
> policy. But I think it's okay to use when it's clearly done
> following a user-command.
Better to explain sequences of Elisp functions considered acceptable and
those that are not with regard to input focus handling and frame stacking.
Bob
[-- Attachment #2: Type: text/html, Size: 2671 bytes --]
next prev parent reply other threads:[~2017-12-13 15:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 23:02 select-frame-set-input-focus fails to raise the frame Bob Weiner
2017-12-12 23:26 ` Robert Weiner
2017-12-13 20:47 ` Alan Third
2017-12-13 22:00 ` Robert Weiner
2017-12-13 22:26 ` Alan Third
2017-12-14 0:33 ` Robert Weiner
2017-12-14 21:03 ` Robert Weiner
2017-12-15 15:53 ` Robert Weiner
2017-12-15 16:10 ` Eli Zaretskii
2017-12-15 17:38 ` Robert Weiner
2017-12-15 20:44 ` Eli Zaretskii
2017-12-16 13:41 ` Robert Weiner
2017-12-16 14:39 ` Eli Zaretskii
2017-12-16 15:06 ` Robert Weiner
2017-12-16 16:15 ` Eli Zaretskii
2017-12-16 18:57 ` Robert Weiner
2017-12-16 19:45 ` Eli Zaretskii
2017-12-16 20:07 ` Robert Weiner
2017-12-16 19:06 ` martin rudalics
2017-12-16 19:24 ` Robert Weiner
2017-12-13 8:50 ` martin rudalics
2017-12-13 15:00 ` Robert Weiner [this message]
2017-12-13 16:07 ` Stefan Monnier
2017-12-13 16:33 ` Robert Weiner
2017-12-13 19:39 ` Eli Zaretskii
2017-12-13 19:30 ` martin rudalics
2017-12-13 22:14 ` Robert Weiner
2017-12-13 20:49 ` Alan Third
2017-12-13 21:53 ` Robert Weiner
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=CA+OMD9h8EHvDBV-w_sXBu-Oy_nco7LVJN2_3R+gsOiuD_dtaeg@mail.gmail.com \
--to=rsw@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rswgnu@gmail.com \
--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 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).