From: Eduardo Ochs <eduardoochs@gmail.com>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Long delay after M-x commandname
Date: Sun, 10 Oct 2021 21:45:39 -0300 [thread overview]
Message-ID: <CADs++6iEZqDd4_+BnPnB_2bYykCG45w2aSc=T_dqm2p6cggCPA@mail.gmail.com> (raw)
Hi list,
this is not a bug report YET - I am looking for more information
first.
Yesterday I noticed that when I was invoking commands with M-x
commandname and using tab for completing parts of the name then
sometimes there would be a long delay - sometimes as long as 10
seconds, but my laptop is quite old - between the RET and the
execution of the command. This delay was big on emacs28 and
practically imperceptible on emacs27. I have several versions of
emacs28 here, with names like emacs28_512 for the one correponding to
HEAD~512 and emacs28_0 for HEAD, and I noticed that this delay was
growing in recent versions: small in HEAD~256, bigger in HEAD~128,
much bigger in HEAD~0.
I _guess_ that these delays are caused by the code that generates
messages like this one:
You can run the command `find-eev-install-intro' with `M-x f--i-i'.
What do I need to learn to understand what is going on, and to prepare
a proper bug report? A quick grepping shows that this message is
generated by `execute-extended-command' in simple.el, but what else?
Thanks in advance,
Eduardo Ochs
http://angg.twu.net/#eev
next reply other threads:[~2021-10-11 0:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 0:45 Eduardo Ochs [this message]
2021-10-11 4:03 ` Long delay after M-x commandname 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
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='CADs++6iEZqDd4_+BnPnB_2bYykCG45w2aSc=T_dqm2p6cggCPA@mail.gmail.com' \
--to=eduardoochs@gmail.com \
--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).