From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: nljlistbox2@gmail.com, monnier@IRO.UMontreal.CA, 23377@debbugs.gnu.org
Subject: bug#23377: 25.0.93; Completion is extremely slow for insert-char
Date: Tue, 26 Apr 2016 09:34:49 +0300 [thread overview]
Message-ID: <83k2jk27zq.fsf@gnu.org> (raw)
In-Reply-To: <571EEA4A.3020105@cs.ucla.edu> (message from Paul Eggert on Mon, 25 Apr 2016 21:10:50 -0700)
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Mon, 25 Apr 2016 21:10:50 -0700
> Cc: "N. Jackson" <nljlistbox2@gmail.com>, 23377@debbugs.gnu.org
>
> Drew Adams wrote:
> > if the main reason to disable it is for performance in
> > an extreme use case (C-x 8 RET TAB)
>
> It's not that extreme. It's natural for a user to get the whole list and then
> use C-s to find the desired character.
It surprises me that this is perceived as "natural", for an Emacs
user. Do they also use this when completing on file names or buffer
names? I don't think so. So why would we assume they do so in this
case? There are more than 30K names in the list popped up by the
above; how is it "reasonable", let alone economical, to search that
huge list, instead of typing some string to narrow down the list of
completions?
next prev parent reply other threads:[~2016-04-26 6:34 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 0:25 bug#23377: 25.0.93; Completion is extremely slow for insert-char N. Jackson
2016-04-26 1:04 ` Paul Eggert
2016-04-26 2:17 ` Stefan Monnier
2016-04-26 2:51 ` Drew Adams
2016-04-26 4:10 ` Paul Eggert
2016-04-26 5:43 ` Drew Adams
2016-04-26 6:21 ` Eli Zaretskii
2016-04-26 6:34 ` Eli Zaretskii [this message]
2016-04-26 13:27 ` N. Jackson
2016-04-26 20:41 ` Paul Eggert
2016-04-27 1:31 ` N. Jackson
2016-04-26 11:51 ` Stefan Monnier
2016-04-26 15:49 ` Paul Eggert
2016-04-26 16:04 ` Drew Adams
2016-04-26 16:59 ` Paul Eggert
2016-04-26 17:15 ` Eli Zaretskii
2016-04-26 18:52 ` N. Jackson
2016-04-26 19:10 ` Eli Zaretskii
2016-04-27 2:09 ` N. Jackson
[not found] ` <<83r3dsyynq.fsf@gnu.org>
2016-04-26 20:18 ` Drew Adams
2016-04-26 16:27 ` Eli Zaretskii
2016-04-26 23:58 ` John Wiegley
2016-04-27 0:26 ` Paul Eggert
2016-04-27 0:53 ` Lars Magne Ingebrigtsen
2016-04-27 1:19 ` John Wiegley
2016-04-27 7:24 ` Eli Zaretskii
2016-04-27 12:27 ` Stefan Monnier
2016-04-27 19:04 ` John Wiegley
2016-04-27 0:10 ` Stefan Monnier
2016-04-26 6:26 ` Eli Zaretskii
2016-04-27 1:54 ` N. Jackson
2016-04-27 7:21 ` Eli Zaretskii
2016-04-27 15:16 ` N. Jackson
2017-09-30 16:40 ` Noam Postavsky
2017-09-30 20:27 ` N. Jackson
2019-06-25 13:53 ` Lars Ingebrigtsen
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=83k2jk27zq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23377@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=monnier@IRO.UMontreal.CA \
--cc=nljlistbox2@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.
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).