unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Weiner <rsw@gnu.org>
To: Alan Third <alan@idiocy.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: select-frame-set-input-focus fails to raise the frame
Date: Wed, 13 Dec 2017 16:53:20 -0500	[thread overview]
Message-ID: <CA+OMD9hkqA3sH_9uXzJqgSrhnfPKR53sP3b4hRd7cwUKY5Jk0Q@mail.gmail.com> (raw)
In-Reply-To: <20171213204923.GB1621@breton.holly.idiocy.org>

[-- Attachment #1: Type: text/plain, Size: 924 bytes --]

On Wed, Dec 13, 2017 at 3:49 PM, Alan Third <alan@idiocy.org> wrote:

> On Tue, Dec 12, 2017 at 06:02:38PM -0500, Bob Weiner wrote:
> > (defun test ()
> >   (let ((depress-frame (selected-frame))
> >       (release-frame (make-frame)))
> >     (select-frame-set-input-focus depress-frame)
> >     ;; On MacOS, depress-frame is never raised to the top
> >     ;; of the frame stack and never is given input focus
> >     ;; after release-frame is created.
> >     (sit-for 4)
> >     (select-frame-set-input-focus release-frame)))
> >
> > (test)
> >
> > ----------
>
> I feel I’m being a bit dim here, but depress-frame is already raised
> and focused when I run this in the scratch buffer, so I’m unsure how
> to try replicating it.
>

​On macOS for me, the (make-frame) call puts the new frame at the top of
the stack and sets input focus there for me,
so depress-frame is under that.

Bob

[-- Attachment #2: Type: text/html, Size: 1912 bytes --]

      reply	other threads:[~2017-12-13 21:53 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
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 [this message]

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+OMD9hkqA3sH_9uXzJqgSrhnfPKR53sP3b4hRd7cwUKY5Jk0Q@mail.gmail.com \
    --to=rsw@gnu.org \
    --cc=alan@idiocy.org \
    --cc=emacs-devel@gnu.org \
    --cc=rswgnu@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).