unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58634@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#58634: Long delay with blank screen whilst loading desktop at emacs startup
Date: Fri, 21 Oct 2022 12:40:32 +0000	[thread overview]
Message-ID: <Y1KTQAQis91wvwVV@ACM> (raw)
In-Reply-To: <838rl9wh4m.fsf@gnu.org>

Hello, Eli.

On Fri, Oct 21, 2022 at 14:28:09 +0300, Eli Zaretskii wrote:
> > Date: Fri, 21 Oct 2022 08:59:58 +0000
> > Cc: 58634@debbugs.gnu.org, acm@muc.de
> > From: Alan Mackenzie <acm@muc.de>

> > > I don't see why it should irritate: you cannot do anything with Emacs
> > > during that time anyway.

> > It irritates, because it looks like Emacs has crashed.  There is no
> > feedback.  If Emacs really has crashed whilst loading the desktop, how
> > long should the user wait before getting angry?  Again, I propose
> > outputting progress dots, possibly as an enabled by default option.

> I don't see any need for adding this.  Your case seems to be a rare
> one, and doesn't justify such complications.

What is rare about my case?  Assuming the (message "") gets removed from
info.el, there are just 3 things needed for the long delay to happen:
(i) Having a large .emacs.desktop;
(ii) Not encountering any error message during its loading.
(iii) Not getting any messages from flyspell and friends or the OS
during loading.

This will be a common case amongst users.

In particular, the problem is NOT confined to the tty.  It will occur on
GUI sessions, too.  When I tried it out this morning under X, the only
thing which triggered a redisplay was a version conflict error between
CC Mode and js-mode (and some status messages from shell-script-mode
very late in the loading).

My current idea is to count the buffers in desktop-save, and to output a
message:

    Restoring buffers: 127/166

as we restore the buffers.  We already count the buffers as we load
them.

This is NOT complicated.

> > And I propose removing the (message "") from Info-toc-build, and amending
> > what this was designed to do in the proper place, wherever that might be.

> I'm guessing that (message "") was there because originally that
> function was showing progress messages as part of its processing:

>    (or main-file (message "Searching subfile %s..." (car subfiles)))

I think this is the case, yes.  There's not a lot of information about
it in the git log.

> However, this has been commented out 14 years ago, so perhaps nowadays
> it isn't necessary.  Adding Juri to the CC in case he has some
> comments.

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2022-10-21 12:40 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 13:28 bug#58634: Long delay with blank screen whilst loading desktop at emacs startup Alan Mackenzie
2022-10-19 15:49 ` Eli Zaretskii
2022-10-19 19:11   ` Andrea Corallo
2022-10-19 19:58     ` Alan Mackenzie
2022-10-20  5:20       ` Eli Zaretskii
2022-10-20 10:55         ` Alan Mackenzie
2022-10-20 13:07           ` Eli Zaretskii
2022-10-20 15:28             ` Alan Mackenzie
2022-10-20 16:28               ` Eli Zaretskii
2022-10-21  8:59                 ` Alan Mackenzie
2022-10-21 11:28                   ` Eli Zaretskii
2022-10-21 12:40                     ` Alan Mackenzie [this message]
2022-10-21 13:22                       ` Eli Zaretskii
2022-10-21 14:15                         ` Alan Mackenzie
2022-10-21 15:23                           ` Eli Zaretskii
2022-10-21 15:42                             ` Alan Mackenzie
2022-10-21 15:57                               ` Eli Zaretskii
2022-10-21 17:15                                 ` Alan Mackenzie
2022-10-21 18:12                                   ` Eli Zaretskii
2022-10-21 19:01                                     ` Alan Mackenzie
2022-10-21 19:14                                       ` Eli Zaretskii
2022-10-21 20:11                                         ` Alan Mackenzie
2022-10-22  6:26                                           ` Eli Zaretskii
2022-10-22 12:20                                             ` Alan Mackenzie
2022-10-22 13:11                                               ` Eli Zaretskii
2022-10-23 15:22                                                 ` Alan Mackenzie
2022-10-23 16:23                                                   ` Eli Zaretskii
2022-10-23 18:58                                                     ` Alan Mackenzie
2022-10-23 19:11                                                       ` Eli Zaretskii
2022-10-26 16:35                                                         ` Alan Mackenzie
2022-10-26 16:38                                                           ` Eli Zaretskii
2022-10-26 19:39                                                           ` Stefan Kangas
2022-10-27  5:19                                                             ` Eli Zaretskii
2022-10-21 19:09                       ` Stefan Kangas
2022-10-22 17:46                     ` Juri Linkov
2022-10-22 18:33                       ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y1KTQAQis91wvwVV@ACM \
    --to=acm@muc.de \
    --cc=58634@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=juri@linkov.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).