From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Long delay after M-x commandname
Date: Tue, 12 Oct 2021 02:19:10 +0200 [thread overview]
Message-ID: <87ily3w0w1.fsf@web.de> (raw)
In-Reply-To: CADs++6iEZqDd4_+BnPnB_2bYykCG45w2aSc=T_dqm2p6cggCPA@mail.gmail.com
Eduardo Ochs <eduardoochs@gmail.com> writes:
> I _guess_ that these delays are caused by the code that generates
> messages like this one:
Adding to what already has been mentioned: There is a `sit-for' of (by
default) 2 seconds for displaying the found shorter version of the input.
But that doesn't explain 10 seconds.
If you can reproduce your problem, my first debugging approach would be
to enable `debug-on-quit' and hit C-g when there is a delay, and look
what Emacs was actually doing at that moment.
Michael.
next prev parent reply other threads:[~2021-10-12 0:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 0:45 Long delay after M-x commandname Eduardo Ochs
2021-10-11 4:03 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-10-11 12:07 ` Eli Zaretskii
2021-10-12 10:07 ` Michael Heerdegen
2021-10-12 0:19 ` Michael Heerdegen [this message]
2021-10-12 1:05 ` Eduardo Ochs
2021-10-12 1:59 ` Michael Heerdegen
2021-10-12 9:52 ` Michael Heerdegen
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=87ily3w0w1.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@gnu.org \
/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.
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).