From: Klymak Jody <jklymak@uvic.ca>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: Adrian Robert <Adrian.B.Robert@gmail.com>,
1437@emacsbugs.donarmstrong.com
Subject: bug#1437: 23.0.60; ido-mode unresponsive once new filename typed
Date: Fri, 28 Nov 2008 13:14:26 -0800 [thread overview]
Message-ID: <E90F6D0C-01BD-4944-A4E4-40197ECD7BB4@uvic.ca> (raw)
In-Reply-To: <87prkhb154.fsf@cyd.mit.edu>
On Nov 27, 2008, at 8:10 AM, Chong Yidong wrote:
>> I am using ido-mode, the following works fine on previous emacsen.
>>
>> If I try and open a file in a directory that does not exist, ido
>> hangs
>> with a "Searching for 'newfile'..." I have to "Force Quit" emacs.
>> Old Emacsen would allow me to keep typing or create a new file by
>> hitting return.
>
> I can't reproduce this on GNU/Linux. It could be a nextstep-only bug.
> Could you provide an exact recipe, starting with `emacs -Q'?
/Applications/Emacs23.app/Contents/MacOS/Emacs -Q
eval: (require 'ido) (ido-mode t)
C-x C-f newfi
ido says "Searching for 'newfi'...." and hangs if there is no
"newfile" in the current directory.
It does seem to eventually come back, but it is a few minutes. It
uses substantial cpu cycles, and there appears to be a fair bit of
data being read from disk. When it comes back it has sometimes found a
suitable suggestion in another directory. Thats nice, but I can't
interrupt the search to type the proper name in. ido on Emacs 22
seems fine.
Please let me know how else I can help debug this.
Cheers, Jody
--
Jody Klymak
http://web.uvic.ca/~jklymak/
next prev parent reply other threads:[~2008-11-28 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-27 16:10 bug#1437: 23.0.60; ido-mode unresponsive once new filename typed Chong Yidong
2008-11-28 21:14 ` Klymak Jody [this message]
2008-11-29 0:44 ` Adrian Robert
2008-11-29 1:14 ` Klymak Jody
-- strict thread matches above, loose matches on Subject: below --
2008-11-27 0:28 Klymak Jody
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=E90F6D0C-01BD-4944-A4E4-40197ECD7BB4@uvic.ca \
--to=jklymak@uvic.ca \
--cc=1437@emacsbugs.donarmstrong.com \
--cc=Adrian.B.Robert@gmail.com \
--cc=cyd@stupidchicken.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).