From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Robert Weiner Newsgroups: gmane.emacs.devel Subject: Re: select-frame-set-input-focus fails to raise the frame Date: Fri, 15 Dec 2017 12:38:15 -0500 Message-ID: References: <20171213204737.GA1621@breton.holly.idiocy.org> <20171213222634.GA2144@breton.holly.idiocy.org> <831sjwt1jf.fsf@gnu.org> Reply-To: rswgnu@gmail.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a1147ab20f9f07d05606478a2" X-Trace: blaine.gmane.org 1513359565 13597 195.159.176.226 (15 Dec 2017 17:39:25 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 15 Dec 2017 17:39:25 +0000 (UTC) Cc: Alan Third , emacs-devel To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Dec 15 18:39:21 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ePtxA-0003DI-Qa for ged-emacs-devel@m.gmane.org; Fri, 15 Dec 2017 18:39:21 +0100 Original-Received: from localhost ([::1]:47890 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ePtxI-0006e2-4d for ged-emacs-devel@m.gmane.org; Fri, 15 Dec 2017 12:39:28 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42875) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ePtwh-0006dh-9i for emacs-devel@gnu.org; Fri, 15 Dec 2017 12:38:52 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ePtwd-0007gI-CF for emacs-devel@gnu.org; Fri, 15 Dec 2017 12:38:51 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:43311) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ePtwd-0007g5-8i for emacs-devel@gnu.org; Fri, 15 Dec 2017 12:38:47 -0500 Original-Received: from mail-qk0-f171.google.com ([209.85.220.171]:41032) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1ePtwc-0003RK-LU; Fri, 15 Dec 2017 12:38:46 -0500 Original-Received: by mail-qk0-f171.google.com with SMTP id r184so3597911qke.8; Fri, 15 Dec 2017 09:38:46 -0800 (PST) X-Gm-Message-State: AKGB3mLSYXyi3x93NA7b2upPZPsfeYmO+0Fs9+ohZ5FFqT19a7JZo9vX 9zEKgNxkGhnfA9rdEbC/lsdZOkd/t2xGafSE0TM= X-Google-Smtp-Source: ACJfBov6Qc54Sm0lw9/rvYLmgIITf8cq4+tsBUOouTD+8L3sgNhZwYhwE3Hlt7QonHOKI/cegh0pISkgPPNo2xme5ps= X-Received: by 10.55.21.150 with SMTP id 22mr18842130qkv.102.1513359526191; Fri, 15 Dec 2017 09:38:46 -0800 (PST) Original-Received: by 10.200.55.124 with HTTP; Fri, 15 Dec 2017 09:38:15 -0800 (PST) In-Reply-To: <831sjwt1jf.fsf@gnu.org> X-Gmail-Original-Message-ID: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:221107 Archived-At: --001a1147ab20f9f07d05606478a2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Dec 15, 2017 at 11:10 AM, Eli Zaretskii wrote: > > From: Robert Weiner > > Date: Fri, 15 Dec 2017 10:53:59 -0500 > > Cc: emacs-devel > > > > 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? > =E2=80=8BThe 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 --001a1147ab20f9f07d05606478a2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Dec 15, 2= 017 at 11:10 AM, Eli Zaretskii <e= liz@gnu.org> wro= te:
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">> 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).=C2=A0 Is that a bug= ?

How do you know Emacs didn't redisplay the window?=C2=A0 "F= orce 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.=C2=A0 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?

= =E2=80=8BThe problem was that I would set-window-buffer in the new frame
t= o a different buffer and that buffer would not display when
the new frame = was brought frontmost and displayed temporarily
with a sleep-for delay.=C2= =A0 Calling force-window-update had no
effect but calling (redisplay t) re= solved it.

Bob


--001a1147ab20f9f07d05606478a2--