From: Drew Adams <drew.adams@oracle.com>
To: Daniel Colascione <dancol@dancol.org>, 16251@debbugs.gnu.org
Subject: bug#16251: 24.3.50; `icomplete-mode' breaks my file opening now
Date: Wed, 25 Dec 2013 09:23:15 -0800 (PST) [thread overview]
Message-ID: <28ae7ba4-fea2-44ae-8cc9-3e026e6b72fb@default> (raw)
In-Reply-To: <52BA978F.4010804@dancol.org>
> Why is finding the list of files so slow for you?
I don't know. And I don't have time right now to track it down.
But I'll try to take a look later some time.
> Don't you experience the same performance problem after typing
> a character and forcing completions to show up?
No, absolutely not.
> We call the completion function inside while-no-input, so we
> should abort the "several seconds" of work as soon as you start
> typing.
I didn't start typing. In Icicles it often makes sense to show
all initial completions from the outset, either automatically or
on demand.
While waiting for better understanding of the problem, and
possibly a fix if there is in fact a bug and solution, I will
automatically turn off `icomplete-show-matches-on-no-input'
when Icicle mode is turned on.
BTW, there is no such problem with using IswitchB with Icicles,
AFAIK.
next prev parent reply other threads:[~2013-12-25 17:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-25 5:58 bug#16251: 24.3.50; `icomplete-mode' breaks my file opening now Drew Adams
2013-12-25 6:18 ` Jambunathan K
2013-12-25 17:17 ` Drew Adams
2013-12-25 8:30 ` Daniel Colascione
2013-12-25 17:23 ` Drew Adams [this message]
2013-12-25 18:02 ` Eli Zaretskii
2013-12-27 12:59 ` Stefan Monnier
2013-12-28 0:55 ` Drew Adams
2013-12-28 8:51 ` Eli Zaretskii
[not found] <<497ebd3d-d69b-4ac4-9d8c-ca2f4a1a2ac1@default>
[not found] ` <<jwv4n5uv4fz.fsf-monnier+emacsbugs@gnu.org>
[not found] ` <<818df3a7-a5fa-4871-86e1-0bd5d8e4a5fc@default>
[not found] ` <<83y5352wae.fsf@gnu.org>
2013-12-28 16:01 ` 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=28ae7ba4-fea2-44ae-8cc9-3e026e6b72fb@default \
--to=drew.adams@oracle.com \
--cc=16251@debbugs.gnu.org \
--cc=dancol@dancol.org \
/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).