unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Weiner <rsw@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Alan Third <alan@idiocy.org>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: select-frame-set-input-focus fails to raise the frame
Date: Fri, 15 Dec 2017 12:38:15 -0500	[thread overview]
Message-ID: <CA+OMD9hzD+1xJFrzAA2_gXfRM=GZ0x8mnWqO=sa29pf3MAJihQ@mail.gmail.com> (raw)
In-Reply-To: <831sjwt1jf.fsf@gnu.org>

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

On Fri, Dec 15, 2017 at 11:10 AM, Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Robert Weiner <rsw@gnu.org>
> > Date: Fri, 15 Dec 2017 10:53:59 -0500
> > Cc: emacs-devel <emacs-devel@gnu.org>
> >
> > Although from the function doc strings, it seems a force-window-update
> > followed by a (sit-for 0) should force redisplay of the chosen window,
> it did
> > not (see the test2 function in the prior message).  Is that a bug?
>
> How do you know Emacs didn't redisplay the window?  "Force redisplay"
> doesn't necessarily mean you will see on display what you think you
> should see, it just means Emacs will consider that window for
> redisplay.  Whether that causes Emacs to show what you think it should
> is another matter entirely: the display engine has its own ideas what
> part(s) of the window need to be redrawn, if any.
>
> I actually don't understand the idea of your test2 function: can you
> tell what you intended to see happen, and why?
>

​The problem was that I would set-window-buffer in the new frame
to a different buffer and that buffer would not display when
the new frame was brought frontmost and displayed temporarily
with a sleep-for delay.  Calling force-window-update had no
effect but calling (redisplay t) resolved it.

Bob

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

  reply	other threads:[~2017-12-15 17:38 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 [this message]
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+OMD9hzD+1xJFrzAA2_gXfRM=GZ0x8mnWqO=sa29pf3MAJihQ@mail.gmail.com' \
    --to=rsw@gnu.org \
    --cc=alan@idiocy.org \
    --cc=eliz@gnu.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).