From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs-26.0.91: switch-to-buffer-other-window runs too slowly (about 0.1s) Date: Mon, 26 Mar 2018 21:33:54 +0300 Message-ID: <83y3ieelf1.fsf@gnu.org> References: <83efk6g93z.fsf@gnu.org> <544b8346-bda9-45eb-9573-1d51d9f768b2@Spark> <83bmfag8gu.fsf@gnu.org> <87y3ie24z1.fsf@gmail.com> <87sh8m23tc.fsf@gmail.com> <87k1ty22p1.fsf@gmail.com> <837epyg30w.fsf@gnu.org> <83370mg0qj.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1522089123 32195 195.159.176.226 (26 Mar 2018 18:32:03 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 26 Mar 2018 18:32:03 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Mar 26 20:31:59 2018 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 1f0WuU-0008Fb-71 for ged-emacs-devel@m.gmane.org; Mon, 26 Mar 2018 20:31:58 +0200 Original-Received: from localhost ([::1]:58457 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f0WwX-0002h5-Lj for ged-emacs-devel@m.gmane.org; Mon, 26 Mar 2018 14:34:05 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44804) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f0WwH-0002Yn-5y for emacs-devel@gnu.org; Mon, 26 Mar 2018 14:33:50 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f0WwD-0006Ql-7u for emacs-devel@gnu.org; Mon, 26 Mar 2018 14:33:49 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:51538) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f0WwD-0006Qe-4j; Mon, 26 Mar 2018 14:33:45 -0400 Original-Received: from [176.228.60.248] (port=3521 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1f0WwC-00085p-Ee; Mon, 26 Mar 2018 14:33:45 -0400 In-reply-to: (message from Stefan Monnier on Mon, 26 Mar 2018 14:26:46 -0400) 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:224063 Archived-At: > From: Stefan Monnier > Cc: emacs-devel@gnu.org > Date: Mon, 26 Mar 2018 14:26:46 -0400 > > But I think in the case where we move from window A to window B and both > are on the same frame we should either not call > window--maybe-raise-frame or else that function should do nothing in > that case. Basically, I feel like if the movement is intra-frame than > no frame-level operations should be involved. I actually don't understand why we wait for MapNotify inside x_make_frame_visible when the frame was already visible. And the fact that it takes almost exactly 100 msec tells me that we never get the event anyway. I'm not an expert on X events -- do we even need to wait in this case?