bug#58634: Long delay with blank screen whilst loading desktop at emacs startup

[Eli Zaretskii]

> 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?