bug#1437: 23.0.60; ido-mode unresponsive once new filename typed

bug#1437: 23.0.60; ido-mode unresponsive once new filename typed

[Klymak Jody]

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.

Thanks,  Jody



In GNU Emacs 23.0.60.1 (i386-apple-darwin9.5.0, NS apple-appkit-949.35)
  of 2008-11-07 on saturna.seos.uvic.ca
Windowing system distributor `Apple', version  
97.112.112.108.101.45.97.112.112.107.105.116.45.57.52.57.46.51.53
configured using `configure  '--with-ns''

Important settings:
   value of $LC_ALL: nil
   value of $LC_COLLATE: nil
   value of $LC_CTYPE: nil
   value of $LC_MESSAGES: nil
   value of $LC_MONETARY: nil
   value of $LC_NUMERIC: nil
   value of $LC_TIME: nil
   value of $LANG: nil
   value of $XMODIFIERS: nil
   locale-coding-system: nil
   default-enable-multibyte-characters: t

Major mode: Fundamental

Minor modes in effect:
   dired-omit-mode: t
   cua-mode: t
   tooltip-mode: t
   mouse-wheel-mode: t
   menu-bar-mode: t
   file-name-shadow-mode: t
   global-font-lock-mode: t
   global-auto-composition-mode: t
   auto-encryption-mode: t
   auto-compression-mode: t
   line-number-mode: t
   transient-mark-mode: t

Recent input:
<help-echo> <menu-bar> <help-menu> <send-emacs-bug
-report>

Recent messages:
Source file `/Users/jklymak/emacs-common/muse/lisp/muse-project.el'  
newer than byte-compiled file
Source file `/Users/jklymak/emacs-common/muse/lisp/muse-publish.el'  
newer than byte-compiled file
Source file `/Users/jklymak/emacs-common/muse/lisp/muse-html.el' newer  
than byte-compiled file
Loading /Users/jklymak/emacs-common/emacs-wiki-functions.el  
(source)...done
Loading /Users/jklymak/emacs-common/planner-config.el (source)...done
Source file `/Applications/Emacs23.app/Contents/Resources/lisp/ido.el'  
newer than byte-compiled file
Ido mode enabled
Loading /Users/jklymak/.gemacs/init.el (source)...done
Loading /Users/jklymak/.gemacs/custom.el (source)...done
For information about GNU Emacs and the GNU system, type C-h C-a.

bug#1437: 23.0.60; ido-mode unresponsive once new filename typed

[Chong Yidong]

> 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'?

bug#1437: 23.0.60; ido-mode unresponsive once new filename typed

[Klymak Jody]

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/

bug#1437: 23.0.60; ido-mode unresponsive once new filename typed

[Adrian Robert]

On Nov 28, 2008, at 4:14 PM, Klymak Jody wrote:

>
> 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

Can't replicate this by starting the Emacs -Q from the emacs src  
directory, setting ido-mode, and then trying "C-x C-f newdir/foo  
<Ret>".  Is there anything unusual about which dir you sit in when  
executing the emacs command, or what type of dir or filename you have  
to type in?  Do you have any NFS or other network mounts?

bug#1437: 23.0.60; ido-mode unresponsive once new filename typed

[Klymak Jody]

On Nov 28, 2008, at  16:44 PM, Adrian Robert wrote:

>
> On Nov 28, 2008, at 4:14 PM, Klymak Jody wrote:
>
>>
>> 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
>
> Can't replicate this by starting the Emacs -Q from the emacs src  
> directory, setting ido-mode, and then trying "C-x C-f newdir/foo  
> <Ret>".  Is there anything unusual about which dir you sit in when  
> executing the emacs command, or what type of dir or filename you  
> have to type in?  Do you have any NFS or other network mounts?

OK, I removed .ido.last and the problem seems to have gone away.   
Perhaps some sort of incompatibility between the two?

I did not have any network drives mounted.

Sorry if this was a config error that I should have figured out on my  
own.

Cheers,  Jody

--
Jody Klymak
http://web.uvic.ca/~jklymak/