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: Fri, 21 Oct 2022 22:14:45 +0300 Message-ID: <83lep9ugyi.fsf@gnu.org> References: <838rl9wh4m.fsf@gnu.org> <834jvxwbuf.fsf@gnu.org> <8335bhw68r.fsf@gnu.org> <83zgdpuq3b.fsf@gnu.org> <83r0z1uju2.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24336"; mail-complaints-to="usenet@ciao.gmane.io" Cc: acm@muc.de, 58634@debbugs.gnu.org, juri@linkov.net To: Alan Mackenzie Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Oct 21 21:48:46 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 1oly0b-00069C-Lo for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 21 Oct 2022 21:48:45 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1olxyy-00024L-C3; Fri, 21 Oct 2022 15:47:04 -0400 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 1olxTz-0001S0-GF for bug-gnu-emacs@gnu.org; Fri, 21 Oct 2022 15:15:04 -0400 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 1olxTz-0002VV-6p for bug-gnu-emacs@gnu.org; Fri, 21 Oct 2022 15:15:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1olxTy-0003qk-D8 for bug-gnu-emacs@gnu.org; Fri, 21 Oct 2022 15:15:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 21 Oct 2022 19:15:02 +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.166637969914774 (code B ref 58634); Fri, 21 Oct 2022 19:15:02 +0000 Original-Received: (at 58634) by debbugs.gnu.org; 21 Oct 2022 19:14:59 +0000 Original-Received: from localhost ([127.0.0.1]:39050 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1olxTv-0003qE-7e for submit@debbugs.gnu.org; Fri, 21 Oct 2022 15:14:59 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:45722) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1olxTp-0003px-U7 for 58634@debbugs.gnu.org; Fri, 21 Oct 2022 15:14:57 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1olxTj-0002NK-Kv; Fri, 21 Oct 2022 15:14:47 -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=6S2YOP26Ll0FBoDhnUfxD1fzG1xfUWHuDz97riMHfLs=; b=Zu/57Ld1/TbT +ceA0vg+JecZMoFYGO6DilpUVeEKLpwqxjUPEmPsd9tsgDLHJmMEU5dJJCyVvlXwTCvGp7zJsdCTo AlcMIsi05HyjN3NDbM1BrKM0S2Was/kQrKljihqp+8pmjJ4ceDE9pzNo2uxRm2jJwPQ30dInlhPaR Tw2n5qw1LAEl/Z8bno+qcERWJTIFVg9h+9zTrxwqOigdIBQEPC9tK4fHTo5xBwxKPKXKc4R9bmeJQ MsvMNCXxEiAv2MTKsvPfi6JD52ehpoCFNsKnTKhaY4EixD+JnC6k01Ommk7USOXo1F3eFTVM+8XWP YK2RQPTz9xuFPrMV0iYwAw==; Original-Received: from [87.69.77.57] (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 1olxTi-0005oT-W0; Fri, 21 Oct 2022 15:14:47 -0400 In-Reply-To: (message from Alan Mackenzie on Fri, 21 Oct 2022 19:01:52 +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: , Original-Sender: "bug-gnu-emacs" Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:246009 Archived-At: > Date: Fri, 21 Oct 2022 19:01:52 +0000 > Cc: juri@linkov.net, 58634@debbugs.gnu.org, acm@muc.de > From: Alan Mackenzie > > > If you want some messages to be displayed, you should be able to > > sprinkle your init file with them, right? > > No. I want reassurance that my Emacs hasn't hung completely, and giving > some indication of how long it's going to be busy is also wanted. Random > messages from .emacs won't help, here. > > > You can also define a desktop-after-read-hook function to display > > something, if you want. > > I wasn't aware of this hook. Being run just once at the end of > desktop-read, it doesn't look like it can be used to provide any > information about the progress of that desktop-read. I think if you enable garbage-collection-messages in your init file, you will see more traffic in the echo area. I'm even okay with adding a hook after each buffer is restored, if that will make you happy. I just don't want these messages (or anything similar) show by default, because no one wants them badly enough. desktop.el is a very old package, so people (myself included) have been using it for decades without being irritated by these problems. It really is an irritation peculiar to your configuration and your state of mind. (There's nothing wrong about having peculiar configurations and states of mind.) > > Assuming this will make the frame display something, why impose your > > personal preferences on everyone? > > That's not fair. One could make the same insinuation against anybody who > added an option for users. It isn't an "insinuation", it's a call to all of us to exercise some self-restraint in imposing on all users solutions for problems that are peculiar to our personal setups. > > I'm not aware of any complaints about what happens when desktop.el > > restores a session (one more reason to consider your case a rare one). > > We simply don't know how common it is. It's the sort of phenomenon that > irritates, but not enough to be bothered to do anything about it. We may not know how common the display issue is, but we do know how common the irritation is: extremely uncommon, to say the least.