unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sean Whitton <spwhitton@spwhitton.name>
To: Eli Zaretskii <eliz@gnu.org>
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: Fri, 04 Oct 2024 19:02:27 +0800	[thread overview]
Message-ID: <87a5fkyvuk.fsf@melete.silentflame.com> (raw)
In-Reply-To: <86r08wxhpq.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 04 Oct 2024 13:53:05 +0300")

Hello,

On Fri 04 Oct 2024 at 01:53pm +03, Eli Zaretskii wrote:

>> From: Sean Whitton <spwhitton@spwhitton.name>
>> Cc: joaotavora@gmail.com,  72826@debbugs.gnu.org,  juri@linkov.net
>> Date: Fri, 04 Oct 2024 17:02:25 +0800
>>
>> Cases where the old code and new code are different are when the
>> minibuffer prompt contains line breaks.  The new code effectively
>> ignores all parts of the minibuffer prompt except its last line.  I
>> think that's correct, and the old code could have calculated an overly
>> large width if previous lines of the minibuffer prompt were longer than
>> the final line.
>
> So you are saying that the old code never worked correctly for
> minibuffer prompts that include embedded newlines?  Then how come no
> one complained about that before?  This bug is not about incorrect
> result, it's about slow responses, and that's something entirely
> different.

Well, not many people use Icomplete mode, and not many minibuffer
prompts have embedded newlines.

If you prefer I could conditionalise the code so it does exactly the
same as it always did in the minibuffer, and only does something
different when completing in a region in a non-minibuffer?

-- 
Sean Whitton





  reply	other threads:[~2024-10-04 11:02 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
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 [this message]
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

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