From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Eli Zaretskii <eliz@gnu.org>
Newsgroups: gmane.emacs.bugs
Subject: bug#58634: Long delay with blank screen whilst loading desktop at
 emacs startup
Date: Sun, 23 Oct 2022 22:11:16 +0300
Message-ID: <83fsfeqrsb.fsf@gnu.org>
References: <Y1LTpzYym0XJkaWF@ACM> <83r0z1uju2.fsf@gnu.org>
 <Y1LsoJ4sd4CzAAUO@ACM> <83lep9ugyi.fsf@gnu.org>
 <Y1L84BbLQV0tKbFN@ACM> <83h6zwv0ft.fsf@gnu.org>
 <Y1PgAkN6O3CJGrJA@ACM> <83tu3wt34l.fsf@gnu.org>
 <Y1VcHV3IUyb2rfK3@ACM>
 <83sfjeqzjf.fsf@gnu.org> <Y1WO4j3MemSl8/0W@ACM>
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="26421"; mail-complaints-to="usenet@ciao.gmane.io"
Cc: 58634@debbugs.gnu.org, juri@linkov.net
To: Alan Mackenzie <acm@muc.de>
Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Oct 24 05:49:10 2022
Return-path: <bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org>
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 <bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org>)
	id 1omoSb-0006jr-N9
	for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 24 Oct 2022 05:49:09 +0200
Original-Received: from localhost ([::1] helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.90_1)
	(envelope-from <bug-gnu-emacs-bounces@gnu.org>)
	id 1omnHr-0004gk-CL; Sun, 23 Oct 2022 22:33:59 -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 <Debian-debbugs@debbugs.gnu.org>)
 id 1omgOA-0007xr-8E
 for bug-gnu-emacs@gnu.org; Sun, 23 Oct 2022 15:12:03 -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 <Debian-debbugs@debbugs.gnu.org>)
 id 1omgOA-0001e7-0k
 for bug-gnu-emacs@gnu.org; Sun, 23 Oct 2022 15:12:02 -0400
Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1omgO9-0003tJ-KR
 for bug-gnu-emacs@gnu.org; Sun, 23 Oct 2022 15:12:01 -0400
X-Loop: help-debbugs@gnu.org
Resent-From: Eli Zaretskii <eliz@gnu.org>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@gnu.org
Resent-Date: Sun, 23 Oct 2022 19:12:01 +0000
Resent-Message-ID: <handler.58634.B58634.166655230614935@debbugs.gnu.org>
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.166655230614935
 (code B ref 58634); Sun, 23 Oct 2022 19:12:01 +0000
Original-Received: (at 58634) by debbugs.gnu.org; 23 Oct 2022 19:11:46 +0000
Original-Received: from localhost ([127.0.0.1]:46491 helo=debbugs.gnu.org)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <debbugs-submit-bounces@debbugs.gnu.org>)
 id 1omgNt-0003sp-Sa
 for submit@debbugs.gnu.org; Sun, 23 Oct 2022 15:11:46 -0400
Original-Received: from eggs.gnu.org ([209.51.188.92]:54146)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <eliz@gnu.org>) id 1omgNo-0003sY-S6
 for 58634@debbugs.gnu.org; Sun, 23 Oct 2022 15:11:44 -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 <eliz@gnu.org>)
 id 1omgNi-0001VQ-3w; Sun, 23 Oct 2022 15:11:34 -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=g4Bl7sX7j0AZL76YObiqFZxRRtBAQDL9ZAOAKnF7teU=; b=VPOvYEBJLTIO
 W8ktNNOtiR1DBLaxQRHgjBr4eDfVeD/yCU2aS2SO7V/K5FMLoDTFa6VMi2mPQqYUSKrkQWUUh8fFJ
 GccOD1vKGt/VZ6DvFQdfp0zS8xU/9+iCskc16t0wxBp2NjbTiVvnfmZxga1lT+dqRdjSujPlrTG8b
 LZOtysApI08wDdvzpWLqOcPu4znukpb5sCBgZdIvXPMkI1kT2LAQYXmrJkrjYsyU5ejaBqq/CYtFf
 T883VOv1uPDYRe+vOBolK/whF1/UXDl5m2V2QYT9ha/k/EyFI8jF2shRAhMp0VyRiP1mZFTQnKp+Z
 u1y87aX5F+KySngEaCXFHA==;
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 <eliz@gnu.org>)
 id 1omgNh-0005wQ-5d; Sun, 23 Oct 2022 15:11:33 -0400
In-Reply-To: <Y1WO4j3MemSl8/0W@ACM> (message from Alan Mackenzie on Sun, 23
 Oct 2022 18:58:42 +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" <bug-gnu-emacs.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-gnu-emacs>,
 <mailto:bug-gnu-emacs-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-gnu-emacs>
List-Post: <mailto:bug-gnu-emacs@gnu.org>
List-Help: <mailto:bug-gnu-emacs-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-gnu-emacs>,
 <mailto:bug-gnu-emacs-request@gnu.org?subject=subscribe>
Original-Sender: "bug-gnu-emacs" <bug-gnu-emacs-bounces@gnu.org>
Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org
Xref: news.gmane.io gmane.emacs.bugs:246069
Archived-At: <http://permalink.gmane.org/gmane.emacs.bugs/246069>

> Date: Sun, 23 Oct 2022 18:58:42 +0000
> Cc: juri@linkov.net, 58634@debbugs.gnu.org
> From: Alan Mackenzie <acm@muc.de>
> 
> > > OK, I've implemented a solution with a hook.
> 
> > It doesn't seem to be such a solution.  I see the hook you've added,
> > but I also see desktop-echo-progress and desktop-progress-message.
> > Why are those here?  Why is anything needed in addition to the hook
> > and its calls where appropriate?
> 
> What's the point of the hook on its own?  I can't see much.  I think what
> you're suggesting is that every user who wants progress messages should
> have to implement his own version.

Exactly.

> That would be a tremendous waste of
> hackers' time, and is, quite frankly, a ludicrous idea.

I don't think it's ludicrous, and I don't think it will be a waste,
for those few who want these progress reports.  How is it a problem to
show an echo-area message saying something like "Restoring buffer %s"?

> Besides, the
> variable desktop-buffer-count is essential to full progress messages

If that is a running count of buffers, the hook can count by itself:
again, a trivial one-liner.  If that's the total number of buffers in
the list, finding their number is a matter of calling 'length'.

(Not that I really understand why the count is so important.  Your
complaint was that Emacs looks frozen, in which case just showing
messages in the echo-area will go a long way towards making clear it
isn't frozen.  So the count and any kind of "progress report" doesn't
sound very important.  But if it is, doing that in a hook should be
easy enough.)

So I really don't see what is all the fuss here.  I suggested a simple
solution for a problem that evidently affects very few.  Since when
writing a short hook function is deemed a problem for someone with
your experience?  Don't you have hooks in your init files?