From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#58634: Long delay with blank screen whilst loading desktop at emacs startup Date: Thu, 20 Oct 2022 16:07:48 +0300 Message-ID: <83czamy76j.fsf@gnu.org> References: <83edv3zud8.fsf@gnu.org> <837d0vyssv.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18401"; mail-complaints-to="usenet@ciao.gmane.io" Cc: acm@muc.de, 58634@debbugs.gnu.org, akrl@sdf.org To: Alan Mackenzie Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Oct 20 17:32:10 2022 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 1olXWk-0004bU-05 for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 20 Oct 2022 17:32:10 +0200 Original-Received: from localhost ([::1]:43176 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1olXWb-0006jw-OA for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 20 Oct 2022 11:32:02 -0400 Original-Received: from [::1] (helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1olXMk-0002er-0T for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 20 Oct 2022 11:21:50 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59604) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1olVIE-0000qP-7t for bug-gnu-emacs@gnu.org; Thu, 20 Oct 2022 09:09:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:34302) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1olVID-000566-V1 for bug-gnu-emacs@gnu.org; Thu, 20 Oct 2022 09:09:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1olVID-0003j7-Pd for bug-gnu-emacs@gnu.org; Thu, 20 Oct 2022 09:09:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 20 Oct 2022 13:09:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 58634 X-GNU-PR-Package: emacs Original-Received: via spool by 58634-submit@debbugs.gnu.org id=B58634.166627128814252 (code B ref 58634); Thu, 20 Oct 2022 13:09:01 +0000 Original-Received: (at 58634) by debbugs.gnu.org; 20 Oct 2022 13:08:08 +0000 Original-Received: from localhost ([127.0.0.1]:33378 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1olVHM-0003ho-8K for submit@debbugs.gnu.org; Thu, 20 Oct 2022 09:08:08 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:38492) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1olVHK-0003gw-9y for 58634@debbugs.gnu.org; Thu, 20 Oct 2022 09:08:07 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:52280) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1olVHB-0004zc-EI; Thu, 20 Oct 2022 09:08:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=68GVfQ56+IRvRs4wMqxvEV2abwsfkqKwK0/jOsZmvtA=; b=Pxv+ZmOoEA4f NeNrD8+KcrqQ7naGdwt/tjMBfEbC/84QbSZTHTc1H8KOQTiS81EDoy3w0r0FWK260NAyScMeeDhDV viXEgKBOI4Hiyih/pJgAhEaAnWcXFUGCR7mgITPL2K+jvHzEW+QYaG/+nBXEfLzMq43xRk15CbA3g GihbU5N9DZY0+DwILZNhwtaPAHxFtwowF8tLUZPSNYVvEKJGtldbvOeLqtsS2Sx3pRbzHIQnH/Y7P Bnhz5KZ+iKD4Lz0hj6E9wq2w294iH8nJVfDDR+Ko4c+4NXN/RMv/FAXh1xWDiL44UaYVqd8u/GnYZ q9bwJVjkExad9vyGYCBwWQ==; Original-Received: from [87.69.77.57] (port=2212 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1olVH8-0006uq-2O; Thu, 20 Oct 2022 09:07:57 -0400 In-Reply-To: (message from Alan Mackenzie on Thu, 20 Oct 2022 10:55:40 +0000) 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" Xref: news.gmane.io gmane.emacs.bugs:245936 Archived-At: > Date: Thu, 20 Oct 2022 10:55:40 +0000 > Cc: akrl@sdf.org, 58634@debbugs.gnu.org, acm@muc.de > From: Alan Mackenzie > > > Because with Emacs 28 I use desktop.el all the time, and I do see the > > frame displaying some files and messages in the echo-area. > > Remember, the blank screen only happens for me in emacs -nw and on the > linux console, not in GUI X. This has yet to be explained. See below. > > If the same happens for you with Emacs 28, I guess it's somehow > > related to your init files and/or what exactly is in your session. > > For example, my sessions always include some buffers under Text mode > > or its descendants, and those turn on Flyspell mode in my > > configuration; starting Flyspell mode launches the speller as a > > sub-process, and that usually triggers some form of redisplay. In > > addition, I have garbage-collection-messages turned on, so GC-related > > messages are shown in the echo-area, which also is a kind of > > redisplay. Restoring file buffers sometimes produces prompts, e.g. if > > the file is too large or there are local variables there that require > > confirmation -- and those prompts trigger redisplay as well. > > > If you have none of that in your configuration, perhaps desktop.el can > > indeed produce a completely blank frame. Although it sounds strange > > to me, since I never saw anything like that. But it could be because > > I'm used to starting Emacs with my configuration. > > All this supports my hypothesis (above). Anything which is "slow" > causes a redisplay during desktop loading. For each buffer loaded, > there is a switch-to-buffer call, so anything causing a redisplay will > display that buffer. I don't follow this reasoning. Emacs is a single-threaded program, so redisplay or lack thereof cannot be explained by something being "slow". Because once redisplay is triggered, it runs to completion, whether it's "slow" or not. So if redisplay doesn't happen in one case it means it wasn't triggered. Things that trigger redisplay are calls to 'message', to 'sit-for', explicit call to 'redisplay', and some others. > If you agree with me that this needs fixing (I think you do), I have two > ideas on how to fix it: I don't yet see what is the problem we are supposed to fix here. Even if, after we dig deeper into this and understand why the frame stays blank in the console case, why is that a problem that needs fixing?