From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Spencer Baugh <sbaugh@janestreet.com>
Cc: dmitry@gutov.dev, 74561@debbugs.gnu.org, juri@linkov.net
Subject: bug#74561: [PATCH] Allow limiting the size of *Completions*
Date: Thu, 28 Nov 2024 23:12:59 -0500 [thread overview]
Message-ID: <jwvo71yk7s6.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <iercyigfmq8.fsf@janestreet.com> (Spencer Baugh's message of "Wed, 27 Nov 2024 15:25:19 -0500")
> From profiling, the main bottleneck in completion over large
> completion sets is display-completion-list, when there are many
> available candidates.
Hmm... interesting. I expected it would be the computation of faces
from things like `completion-pcm--hilit-commonality`.
Do you happen to know which part of `display-completion-list` is the
most costly? is it the actual insertion into the buffer?
I think we should try and fill the buffer lazily. We don't have much
experience with "jit" populating a buffer (the closest I can think of is
the `vlf` package, which doesn't do "jit", IIRC), so it may take some
trial-and-error until we have something that works, but it
seems worthwhile.
Stefan
next prev parent reply other threads:[~2024-11-29 4:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 20:25 bug#74561: [PATCH] Allow limiting the size of *Completions* Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-27 23:23 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-28 6:42 ` Eli Zaretskii
2024-11-28 18:18 ` Juri Linkov
2024-11-29 2:36 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-29 4:12 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-11-29 14:45 ` Spencer Baugh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 17:17 ` Dmitry Gutov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvo71yk7s6.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=74561@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=juri@linkov.net \
--cc=monnier@iro.umontreal.ca \
--cc=sbaugh@janestreet.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.