How can I debug this?

How can I debug this?

[Leo]

[-- Attachment #1: Type: text/plain, Size: 296 bytes --]

Hi there,

[Emacs unicode-2 branch CVS 2006-11-22]

I see some strange behavior of ido.el but have no idea how to
reproduce it. It just happens once in a while. As shown in the
screenshot, (No matches) gets inserted in the minibuffer with each
keystroke. Any idea how I can track down this bug?


[-- Attachment #2: emacs-ido.png --]
[-- Type: image/png, Size: 1850 bytes --]

[-- Attachment #3: Type: text/plain, Size: 9 bytes --]


-- 
Leo

[-- Attachment #4: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

Re: How can I debug this?

[Kim F. Storm]

Leo <sdl.web@gmail.com> writes:

> Hi there,
>
> [Emacs unicode-2 branch CVS 2006-11-22]
>
> I see some strange behavior of ido.el but have no idea how to
> reproduce it. It just happens once in a while. As shown in the
> screenshot, (No matches) gets inserted in the minibuffer with each
> keystroke. Any idea how I can track down this bug?
>

M-x ido-toggle-trace

.. use ido until the bug happens

M-x ido-toggle-trace

Then you'll have a *IDO Trace* buffer which you can send me to look at.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

Re: How can I debug this?

[martin rudalics]

 >>I see some strange behavior of ido.el but have no idea how to
 >>reproduce it. It just happens once in a while. As shown in the
 >>screenshot, (No matches) gets inserted in the minibuffer with each
 >>keystroke. Any idea how I can track down this bug?

Note that change:

2005-03-21  Stefan Monnier  <monnier@iro.umontreal.ca>

	* icomplete.el: Don't forcibly turn on the mode upon load.
	(icomplete-mode): Use define-minor-mode.

Both ido.el and iswitchb.el use

(icomplete-mode nil)

to silence that up.  FWIW

(icomplete-mode -1)

should remove the problem.

Re: How can I debug this?

[Leo]

On Monday, 27 Nov 2006, martin rudalics wrote:

>>>I see some strange behavior of ido.el but have no idea how to
>>>reproduce it. It just happens once in a while. As shown in the
>>>screenshot, (No matches) gets inserted in the minibuffer with each
>>>keystroke. Any idea how I can track down this bug?
>
> Note that change:
>
> 2005-03-21  Stefan Monnier  <monnier@iro.umontreal.ca>
>
> 	* icomplete.el: Don't forcibly turn on the mode upon load.
> 	(icomplete-mode): Use define-minor-mode.
>
> Both ido.el and iswitchb.el use
>
> (icomplete-mode nil)
>
> to silence that up.  FWIW
>
> (icomplete-mode -1)
>
> should remove the problem.

This is helpful. Thank you.

-- 
Leo

Re: How can I debug this?

[Kim F. Storm]

martin rudalics <rudalics@gmx.at> writes:

>>>I see some strange behavior of ido.el but have no idea how to
>>>reproduce it. It just happens once in a while. As shown in the
>>>screenshot, (No matches) gets inserted in the minibuffer with each
>>>keystroke. Any idea how I can track down this bug?
>
> Note that change:
>
> 2005-03-21  Stefan Monnier  <monnier@iro.umontreal.ca>
>
> 	* icomplete.el: Don't forcibly turn on the mode upon load.
> 	(icomplete-mode): Use define-minor-mode.
>
> Both ido.el and iswitchb.el use
>
> (icomplete-mode nil)
>
> to silence that up.  FWIW
>
> (icomplete-mode -1)
>
> should remove the problem.

Thank you.

That (partially) explains what's going on.

Problem is that ido.el only binds icomplete-mode to nil temporarily,
whereas your suggestion permanently disables icomplete-mode.

I have made a change to icomplete.el so that it will notice (and do
nothing) if icomplete-mode is temporarily bound to nil.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

Re: How can I debug this?

[Leo]

On Tuesday, 28 Nov 2006, Kim F. Storm wrote:

> martin rudalics <rudalics@gmx.at> writes:
>
>>>>I see some strange behavior of ido.el but have no idea how to
>>>>reproduce it. It just happens once in a while. As shown in the
>>>>screenshot, (No matches) gets inserted in the minibuffer with each
>>>>keystroke. Any idea how I can track down this bug?
>>
>> Note that change:
>>
>> 2005-03-21  Stefan Monnier  <monnier@iro.umontreal.ca>
>>
>> 	* icomplete.el: Don't forcibly turn on the mode upon load.
>> 	(icomplete-mode): Use define-minor-mode.
>>
>> Both ido.el and iswitchb.el use
>>
>> (icomplete-mode nil)
>>
>> to silence that up.  FWIW
>>
>> (icomplete-mode -1)
>>
>> should remove the problem.
>
> Thank you.
>
> That (partially) explains what's going on.
>
> Problem is that ido.el only binds icomplete-mode to nil temporarily,
> whereas your suggestion permanently disables icomplete-mode.
>
> I have made a change to icomplete.el so that it will notice (and do
> nothing) if icomplete-mode is temporarily bound to nil.

Does this mean ido and icomplete-mode can be enabled at the same time?

-- 
Leo

Re: How can I debug this?

[Kim F. Storm]

Leo <sdl.web@gmail.com> writes:

> Does this mean ido and icomplete-mode can be enabled at the same time?

Yes.

Ido will (is supposed to) disable icomplete-mode temporarily whenever
it uses the minibuffer.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

Re: How can I debug this?

[Leo]

On Tuesday, 28 Nov 2006, Kim F. Storm wrote:

> Leo <sdl.web@gmail.com> writes:
>
>> Does this mean ido and icomplete-mode can be enabled at the same time?
>
> Yes.
>
> Ido will (is supposed to) disable icomplete-mode temporarily whenever
> it uses the minibuffer.

I have enable icomplete-mode and it seems to work fine this
time. Thanks for the fix.

-- 
Leo