From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.bugs Subject: bug#61667: 29.0.60; Failure to redisplay Date: Tue, 21 Feb 2023 22:53:13 +0200 Message-ID: References: <04d7cb31-684c-07c0-ee7b-503514fc1a85@yandex.ru> <87a617eanz.fsf@yahoo.com> <4306cb76-a44c-3101-e43c-fd64afae4a51@yandex.ru> <871qmje2ws.fsf@yahoo.com> <83edqjtbss.fsf@gnu.org> <4e5e2a46-9b07-206a-6774-9f98f34cbd14@yandex.ru> <83y1orrolh.fsf@gnu.org> <83sfeyswdw.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36525"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Cc: luangruo@yahoo.com, 61667@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Feb 21 21:54:18 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pUZeT-0009Gt-Ng for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 21 Feb 2023 21:54:17 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pUZeI-0000CH-RA; Tue, 21 Feb 2023 15:54:06 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pUZeE-0000B8-OU for bug-gnu-emacs@gnu.org; Tue, 21 Feb 2023 15:54:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pUZeE-0002mV-GD for bug-gnu-emacs@gnu.org; Tue, 21 Feb 2023 15:54:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pUZeE-0005R3-7I for bug-gnu-emacs@gnu.org; Tue, 21 Feb 2023 15:54:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Dmitry Gutov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 21 Feb 2023 20:54:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 61667 X-GNU-PR-Package: emacs Original-Received: via spool by 61667-submit@debbugs.gnu.org id=B61667.167701280420849 (code B ref 61667); Tue, 21 Feb 2023 20:54:02 +0000 Original-Received: (at 61667) by debbugs.gnu.org; 21 Feb 2023 20:53:24 +0000 Original-Received: from localhost ([127.0.0.1]:57323 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pUZdb-0005QB-P3 for submit@debbugs.gnu.org; Tue, 21 Feb 2023 15:53:24 -0500 Original-Received: from mail-wr1-f53.google.com ([209.85.221.53]:41892) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pUZdZ-0005Px-6Q for 61667@debbugs.gnu.org; Tue, 21 Feb 2023 15:53:22 -0500 Original-Received: by mail-wr1-f53.google.com with SMTP id z8so5520932wrm.8 for <61667@debbugs.gnu.org>; Tue, 21 Feb 2023 12:53:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :sender:from:to:cc:subject:date:message-id:reply-to; bh=ceGqD1Bz1Dwk+WUp8rqRkuoPuQT+TiqkReOEzkmJQoU=; b=UteUHCfAR0+FvYjjAmOxqmwGtr+mzKWsTvkk/DVIruFQHxIZ9hBO8CJAeJAGozaUh2 1FKoO2QPIbQm70Zmu3aIG6DPiuZSJWfeBzH5TqjbXXXTh7Kp2hVgapZntOjiOWWfTqJI TgKgUXdnM/TUskAP19QrKC+F9F7lVdHW7gygI2w+yG+RWe66qhASfSa5jOYQFfUHVaIw idce81ffPBAOZOeegUAvjqY/QqXFzFLrGxTcp/azOss+tpDaJWUu4i1UeGIS0aD5nBm9 4TfjcdwcqIpVmYYxjaLpA1NaSUmBSebRzfCbwQnODB4BcRa91XA6eJc6d/4pZEwibDkJ eQPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :sender:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ceGqD1Bz1Dwk+WUp8rqRkuoPuQT+TiqkReOEzkmJQoU=; b=4BeBSidQMoa52eH6fVOPLjKihrb5gyjLpT+EZlFon4eD2zfjLI+/7mz1G9aRcyEtTQ dwL8W2pju1E5R69a5JjZg81LrNOZ0GiwdQ1Tfox9NSO0ncD7l0JCEo6mNAS/ymax6i2Q RBMHu0lMsi8/9l8Yu0sDl0SHpFzlKkX8VSHL+2uD1MUYU6MMO7xYcbUFCEieWvwrqaSF AyStWFJ1mVfzyYshZtKnocx04kd+BRwu1t0agQ/5smUuNwsE6cVtCsulbd0gRxahIbN6 13MkiUX7/om6MKntLoOUivf/QKB8FFC17dQ2oLFgJRuaok3rgpHD4mbGvEgdJiTTyMF7 aVjA== X-Gm-Message-State: AO0yUKUXZ/sW66uonUFEy7Ar/k7lVuciNwqwevvXNnLw7JnhW4wR2xxn r3fXCQ0qMuyADv05t5oJhNM= X-Google-Smtp-Source: AK7set/DyAPIZgvnMzNVdKb5E0R3IVVyUk7rgnqwRiSVFHDCQJBVc2g8i9pdFr77EsrE2JpSVPF0CA== X-Received: by 2002:a05:6000:1049:b0:2c7:6bb:fb7a with SMTP id c9-20020a056000104900b002c706bbfb7amr2440317wrx.54.1677012795177; Tue, 21 Feb 2023 12:53:15 -0800 (PST) Original-Received: from [192.168.0.2] ([46.251.119.176]) by smtp.googlemail.com with ESMTPSA id a16-20020adffb90000000b002c54c92e125sm4485942wrr.46.2023.02.21.12.53.14 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 21 Feb 2023 12:53:14 -0800 (PST) Content-Language: en-US In-Reply-To: <83sfeyswdw.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:256311 Archived-At: On 21/02/2023 20:31, Eli Zaretskii wrote: >> Date: Tue, 21 Feb 2023 19:25:28 +0200 >> Cc: luangruo@yahoo.com, 61667@debbugs.gnu.org >> From: Dmitry Gutov >> >>> I'm not surer I follow: why should a frame resize in this case? You >>> just visit a file in an existing window of an existing frame, right? >>> Or is the situation more complicated? If the latter, please tell the >>> details, they could be relevant. >> >> Given how slow the unoptimized build is, I can usually start (and >> finish) typing the command before Emacs has fully finished processing >> the init script, including the default face customizations (which result >> in frame resizing). >> >>>> So if I wait for it, and then use 'C-x b' (with Ido's support for >>>> recentf), then I also can trigger the problem. >>> >>> Not following again: wait for what? And what happens when you use >>> "C-x b"? >> >> 'C-x b' followed by the file name from history, followed by RET -> >> visiting the previously visited file. From recentf. >> >> This behavior is driven by the option ido-virtual-buffers. Unlikely >> affects something. >> >> But it allows me to shorten the scenario of visiting a file for the >> first time after launching Emacs, so that I can trigger the bug faster >> (over several tries). > > So you: > > . start Emacs > . wait for the initial frame to be redrawn after the init files are > processed > . visit a file by typing "C-x b" and selecting a file from a list > > And then you see an empty window with the frame's title showing the > file you selected. Is that correct? Not exactly empty, just not updated. I guess I was saying it's blank because the scratch is usually displayed as blank. But I wasn't able to repro this with non-empty scratch. Not in the latest experiments, at least. > If so, what do you see on the > mode line as the buffer name? Whatever it was showing before I hit RET. Its contents for *scratch*, I guess. >> Overall, though, the unoptimized build makes it harder to reproduce: >> I've only managed that 3 times, so far. > > Which likely means this is some kind of timing issue. Which perhaps > also explains why trace-redisplay stops it from happening: it slows > down redisplay because it needs to output the traces. So we are > looking at some X or GTK event that comes in and somehow interrupts or > prevents redisplay from doing its job, after it evidently started > (because the frame title is updated at the beginning of a redisplay > cycle)? Or maybe it's something that prevents us from swapping the > double-buffering buffers so that the redrawn stuff is actually shown > on the glass? I understand you are musing here. >> But the echo area is not getting redrawn either: the selection of >> buffers to switch to is still visible as it was when I pressed RET. Just >> the title bar changes. The echo area is updated together with the main >> window showing the buffer. > > The echo area is shown in a window, so that seems to be part of not > updating the windows on display. Yep. Or to be more precise, the whole frame contents are not updated. Just the title. At first.