all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: joaotavora@gmail.com, 72826@debbugs.gnu.org, juri@linkov.net
Subject: bug#72826: 30.0.90; icomplete-in-buffer becomes unusably slow in large Eshell
Date: Thu, 03 Oct 2024 18:16:02 +0300	[thread overview]
Message-ID: <8634ldz07h.fsf@gnu.org> (raw)
In-Reply-To: <8734ldxntq.fsf@melete.silentflame.com> (message from Sean Whitton on Thu, 03 Oct 2024 22:28:49 +0800)

> From: Sean Whitton <spwhitton@spwhitton.name>
> Cc: 72826@debbugs.gnu.org, Juri Linkov <juri@linkov.net>, João Távora
>  <joaotavora@gmail.com>
> Date: Thu, 03 Oct 2024 22:28:49 +0800
> 
>        38958  93% - icomplete-post-command-hook
>        38958  93%  - icomplete-exhibit
>        38819  93%   - icomplete-completions
>        38749  92%      string-width
>           43   0%    + icomplete--sorted-completions
>           27   0%      buffer-string
>          139   0%   + sit-for
> 
> I think the culprit is probably the evaulation of
> (string-width (buffer-string)) in icomplete-completions.

Does it help to disable auto-composition-mode?





  reply	other threads:[~2024-10-03 15:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-27  7:26 bug#72826: 30.0.90; icomplete-in-buffer becomes unusably slow in large Eshell Sean Whitton
2024-08-27 12:43 ` Eli Zaretskii
2024-10-03 14:28   ` Sean Whitton
2024-10-03 15:16     ` Eli Zaretskii [this message]
2024-10-04  0:20       ` Sean Whitton
2024-10-04  6:11         ` Eli Zaretskii
2024-10-04  9:02           ` Sean Whitton
2024-10-04 10:53             ` Eli Zaretskii
2024-10-04 11:02               ` Sean Whitton
2024-10-04 11:52                 ` Eli Zaretskii
2024-10-04 14:09                   ` Sean Whitton
2024-10-04 14:33                     ` Eli Zaretskii
2024-10-05  0:21                       ` Sean Whitton
2024-10-05  7:16                         ` Eli Zaretskii
2024-10-05  7:44                           ` Sean Whitton

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=8634ldz07h.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=72826@debbugs.gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=juri@linkov.net \
    --cc=spwhitton@spwhitton.name \
    /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.