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

[Eli Zaretskii <eliz@gnu.org>]

> Date: Fri, 21 Oct 2022 19:01:52 +0000
> Cc: juri@linkov.net, 58634@debbugs.gnu.org, acm@muc.de
> From: Alan Mackenzie <acm@muc.de>
> 
> > 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.