From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eduardo Ochs <eduardoochs@gmail.com>
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 14:56:40 +0200 [thread overview]
Message-ID: <87ee8qcsfr.fsf@gnus.org> (raw)
In-Reply-To: <CADs++6gr9J3OuNP5KZWnijZuCXO_yaagsE5oPEvYfiQR7ggniw@mail.gmail.com> (Eduardo Ochs's message of "Mon, 11 Oct 2021 23:44:57 -0300")
Eduardo Ochs <eduardoochs@gmail.com> writes:
> 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")
But it's run like this:
(while-no-input (execute-extended-command--shorter "find-eev-quick-intro" "find-eev-qui"))
So typing any key should abort it.
I'm not saying we shouldn't make the function shorter, but what's the
use case where this matters to the user? You mention it affecting
`M-x TAB', but as far as I can see, that function is never called when
doing that?
I tried
M-x debug-on-entry RET execute-extended-command--shorter RET
M-x TAB
and it wasn't called. Do you have a complete recipe, starting from
"emacs -Q", that demonstrates the problem?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-10-12 12:56 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 [this message]
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
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=87ee8qcsfr.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=51143@debbugs.gnu.org \
--cc=eduardoochs@gmail.com \
--cc=michael_heerdegen@web.de \
/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).