all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: acm@muc.de, 58634@debbugs.gnu.org, juri@linkov.net
Subject: bug#58634: Long delay with blank screen whilst loading desktop at emacs startup
Date: Fri, 21 Oct 2022 19:01:52 +0000	[thread overview]
Message-ID: <Y1LsoJ4sd4CzAAUO@ACM> (raw)
In-Reply-To: <83r0z1uju2.fsf@gnu.org>

Hello, Eli.

On Fri, Oct 21, 2022 at 21:12:37 +0300, Eli Zaretskii wrote:
> > Date: Fri, 21 Oct 2022 17:15:19 +0000
> > Cc: juri@linkov.net, 58634@debbugs.gnu.org, acm@muc.de
> > From: Alan Mackenzie <acm@muc.de>

> > Hello, Eli.

> > On Fri, Oct 21, 2022 at 18:57:28 +0300, Eli Zaretskii wrote:
> > > > Date: Fri, 21 Oct 2022 15:42:54 +0000
> > > > Cc: juri@linkov.net, 58634@debbugs.gnu.org, acm@muc.de
> > > > From: Alan Mackenzie <acm@muc.de>

> > > > > I'm against adding this kind of trace.

> > > > Yes, that's clear, but you haven't suggested anything better.  Emacs
> > > > freezing for large portions of a minute, or even longer, is not a good
> > > > thing.

> > > I suggest to do nothing about that.

> > Yes.  I don't understand that.  Emacs hangs irritatingly, and there's a
> > simple fix.  You're not prepared to apply it, to try it out, or even to
> > look at it.

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

> 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.  My "personal preferences" here are a totally
neutral, factual display which is not imposed on anybody; there is a
defcustom to switch that display off.  There is even the possibility of
making its default nil.

> 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.  I've
been irritated by it for quite some time, also irritated in previous
years by random buffers being displayed on my screen at startup without
understanding why.  Now I do understand why, and have made amendments to
my Emacs so that these things don't happen any more.

I was proposing to give users a choice between different sorts of
irritation.  I get irritated at indeterminate waits for something to
happen, you get irritated by half a minute's worth of a counter
incrementing on a screen.  I will solve my personal problem by
incorporating my changes into every current and future version of Emacs
on my machine.

> > What about the other remaining matter - that (message "") in info.el?
> > Presumably we're waiting on some response from Juri.

> Yes.  Assuming my guess is correct, I'm okay with removing that.

OK, thanks!

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2022-10-21 19:01 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=Y1LsoJ4sd4CzAAUO@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.