From: Tassilo Horn <tsdh@gnu.org>
To: Hongyi Zhao <hongyi.zhao@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Too long completion delay time in LISP interaction mode.
Date: Wed, 20 Oct 2021 07:01:24 +0200 [thread overview]
Message-ID: <87tuhcs2ov.fsf@gnu.org> (raw)
In-Reply-To: <CAGP6POJdO98SCJQ7_NPE2jps9P9WanT0JO4CuYSuQNsxj4q=XQ@mail.gmail.com>
Hongyi Zhao <hongyi.zhao@gmail.com> writes:
> On Ubuntu 20.04.3 LTS, I'm using the self compiled Emacs git master
> version. I find there is a very long completion delay time in LISP
> interaction mode. For example, when I type `(map)' in scratch buffer,
> there will have 5070 candidates as shown in the attached file, and the
> completion delay is about 2-5 seconds.
>
> Any hints to improve this phenomenon?
First, I'd try to isolate where the slowdown happens. The screenshots
suggests you are using company-mode with custom hacks to get the
numbering of candidates and you are using some fuzzy completion-style.
So I'd start with emacs -Q and typing (map<TAB> in *scratch* to get the
*Completions* buffer. That will probably be fast but deliver less
results because of the default value of `completion-styles'. Then I'd
try out your settings of `completion-styles' (and
`completion-category-overrides' if you have customized that). Then
again with `company-mode' but first without the numbering hack, and
eventually with it. At which step does it become slow?
Also, using the profiler might shed some light on where the time is
spent, see (info "(elisp) Profiling").
HTH,
Tassilo
next prev parent reply other threads:[~2021-10-20 5:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 3:11 Too long completion delay time in LISP interaction mode Hongyi Zhao
2021-10-20 4:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-10-20 4:27 ` Hongyi Zhao
2021-10-20 5:01 ` Tassilo Horn [this message]
2021-10-20 5:29 ` Hongyi Zhao
2021-10-20 5:49 ` Tassilo Horn
2021-10-20 6:11 ` Hongyi Zhao
2021-10-20 6:19 ` Tassilo Horn
2021-10-20 6:42 ` Hongyi Zhao
2021-10-20 7:20 ` Tassilo Horn
2021-10-20 7:35 ` Hongyi Zhao
2021-10-21 5:32 ` Hongyi Zhao
2021-10-21 5:45 ` Tassilo Horn
2021-10-21 6:14 ` Hongyi Zhao
2021-10-21 8:50 ` Tassilo Horn
2021-10-21 10:38 ` Hongyi Zhao
2021-10-20 7:24 ` Hongyi Zhao
2021-10-20 7:37 ` Tassilo Horn
2021-10-20 9:17 ` Hongyi Zhao
2021-10-20 6:24 ` Hongyi Zhao
2021-10-20 5:58 ` Hongyi Zhao
2021-10-20 15:30 ` [External] : " Drew Adams
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=87tuhcs2ov.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=hongyi.zhao@gmail.com \
/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).