From: Tim Cross <email@example.com>
Subject: Re: Enhancement: M-x (+lag+) command
Date: Mon, 12 Jul 2021 12:20:53 +1000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Ypo <email@example.com> writes:
> When I send M-x and I start to write a command, I write it down to the buffer
> where I have my text, instead of to the new buffer where commands appear.
> So, after I send M-x, I have to wait some time, and then I can write the
> command. There is a lag between M-x and command inputting availability.
> Couldn't this lag be neutralized? For example, by recording every sent key after
> M-x and pasting them down when the commands new buffer is available?
This does not sound like typical behaviour. The first thing which needs
to be established is whether or not this is a local configuration
problem. Start by running
and then opening the org file where you see this issue and see if you
can reproduce the problem. If you cannot, then it is very likely the
issue is due to some configuration or additional package you have
If you can reproduce the problem, then please log a bug report using M-x
org-submit-bug-report. This will generate a buffer with a lot of
important information regarding your local setup and may help us track
down the source of the issue.
If you cannot reproduce the problem with emacs -Q, then the cause is
likely a local configuration or additional package you have installed.
Tracking down the cause might take a bit of work. Essentially, you will
need to reduce your configuration to a minimal setup, test and if there
is no problem, slowly add back bits of your configuration or additional
packages, testing after each change, until you find the cause. Once we
know what the cause is, we can probably provide suggestions/assistance
to get it resolved.
A number of popular add-on packages relating to command input, like
helm, smex, hydra, ivy, counsel etc can cause significant slowdown in
command input if not correctly configured. My suspicion is that one of
these packages is likely the cause.
next prev parent reply other threads:[~2021-07-12 2:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <firstname.lastname@example.org>
2021-07-11 22:00 ` Enhancement: M-x (+lag+) command Ypo
2021-07-12 2:20 ` Tim Cross [this message]
2021-07-12 8:17 ` Eric S Fraga
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).