From: Eli Zaretskii <eliz@gnu.org>
To: Eduardo Ochs <eduardoochs@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: michael_heerdegen@web.de, 51143@debbugs.gnu.org
Subject: bug#51143: 29.0.50; Long delay after M-x commandname
Date: Tue, 12 Oct 2021 16:39:32 +0300 [thread overview]
Message-ID: <83ee8qqs4r.fsf@gnu.org> (raw)
In-Reply-To: <CADs++6gr9J3OuNP5KZWnijZuCXO_yaagsE5oPEvYfiQR7ggniw@mail.gmail.com> (message from Eduardo Ochs on Mon, 11 Oct 2021 23:44:57 -0300)
> From: Eduardo Ochs <eduardoochs@gmail.com>
> Date: Mon, 11 Oct 2021 23:44:57 -0300
>
> 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, and
> it seemed that it was getting worse in more recent versions of
> emacs28/29.
>
> I discussed this on help-gnu-emacs before submitting a bug report. The
> main links are these ones:
>
> https://lists.gnu.org/archive/html/help-gnu-emacs/2021-10/msg00232.html Edrx
> https://lists.gnu.org/archive/html/help-gnu-emacs/2021-10/msg00259.html MH
> https://lists.gnu.org/archive/html/help-gnu-emacs/2021-10/msg00261.html Edrx 2
> https://lists.gnu.org/archive/html/help-gnu-emacs/2021-10/msg00265.html MH 2
>
> Let me summarize. The part of "M-x commandname" that takes a long time
> is the call to `execute-extended-command--shorter' - like this:
>
> (execute-extended-command--shorter "find-eev-quick-intro" "find-eev-qui")
>
> Michael Heerdegen was able to reproduce the problem and profile it.
> See this message:
>
> https://lists.gnu.org/archive/html/help-gnu-emacs/2021-10/msg00265.html MH 2
Stefan, any advice?
next prev parent reply other threads:[~2021-10-12 13:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 2:44 bug#51143: 29.0.50; Long delay after M-x commandname Eduardo Ochs
2021-10-12 12:56 ` Lars Ingebrigtsen
2021-10-12 19:05 ` Eduardo Ochs
2021-10-12 19:19 ` Lars Ingebrigtsen
2021-11-29 19:25 ` Lars Ingebrigtsen
2021-11-29 20:11 ` Michael Heerdegen
2021-11-29 20:13 ` Lars Ingebrigtsen
2022-09-12 11:50 ` Lars Ingebrigtsen
2022-09-15 9:49 ` Michael Heerdegen
2022-10-03 22:40 ` Michael Heerdegen
2022-10-03 23:33 ` Lars Ingebrigtsen
2022-10-09 18:53 ` Michael Heerdegen
2021-10-12 13:39 ` Eli Zaretskii [this message]
2021-10-12 15:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83ee8qqs4r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51143@debbugs.gnu.org \
--cc=eduardoochs@gmail.com \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
/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).