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: Thu, 14 Dec 2017 16:03:31 -0500	[thread overview]
Message-ID: <CA+OMD9jySwm=-PFBZwO13eHEQi5_-UurBEGaY-9UVxQ7EszGMw@mail.gmail.com> (raw)
In-Reply-To: <CA+OMD9gxCqetg_mzke2cxR0ok9J10WTon694Rkrb8EaCAS2FrA@mail.gmail.com>

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

On Wed, Dec 13, 2017 at 7:33 PM, Robert Weiner <rsw@gnu.org> wrote:

> The combination of (sit-for 0) to cause
> redisplay followed by a (sleep-for <n>) solved the problem
> completely​ for me.
>

​Well, one more problem remains here.  If the new frame is created with
its window showing buffer1 and then set-window-buffer is used to
change it to buffer2 (or even if switch-to-buffer is used), buffer2 is
not displayed ​when the new frame is temporarily displayed (buffer1 is).
Not until after Emacs becomes idle agai is buffer2 displayed in this new
frame.

I have tried using sit-for, sleep-for, force-mode-line-update and
force-window-update but none of these seem to make redisplay show
buffer2 in the new frame.

Buffer2 is not known at the time of the new frame creation, so I can't
create it with that as the default.

(defun test2 ()
  (let ((depress-frame (selected-frame))
        (release-frame (make-frame)))
    (set-window-buffer (frame-selected-window release-frame) "*scratch*")
    (sit-for 0)
    (sleep-for 2)
    (select-frame-set-input-focus depress-frame)
    (sit-for 0)
    (sleep-for 2)
    (select-frame-set-input-focus release-frame)))

(test2)

Bob​

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

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

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+OMD9jySwm=-PFBZwO13eHEQi5_-UurBEGaY-9UVxQ7EszGMw@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).