emacs-pretest-bug
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Loop in coding.c (was: Re: its possible to make emacs not respond wi


From: Kenichi Handa
Subject: Re: Loop in coding.c (was: Re: its possible to make emacs not respond with ido mode)
Date: Sun, 05 Jun 2005 17:59:06 +0900
User-agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/22.0.50 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI)

In article <address@hidden>, address@hidden (Kim F. Storm) writes:

> Handa-san, can you pls. verify the patch below.

> Stefan Monnier <address@hidden> writes:

>>>>  - This is annoying and time consuming, so i press c-g. However, ido
>>>>  doesnt stop looking, so I get annoyed and press c-g several times
>>>>  quickly.
>> 
>>  I recommend the use of while-no-input for such cases (I actually wrote the
>>  first version of it when working on icomplete.el).

> The problem is a loop in decode_coding_string.  It does not check
> for the CODING_FINISH_INTERRUPT return value from decode_coding (QUIT).
> So once the user signal quit, there is no escape from that loop...

> The following patch seems to fix it, but I'm not sure it is the correct
> thing to do.  

Yes, the patch is correct.   But, it's strange.  I remember
I installed something like that long ago.  And, ChangeLog
surely has this entry.

2004-06-11  Kenichi Handa  <address@hidden>

        * coding.c (decode_coding_string): Check CODING_FINISH_INTERRUPT.

Anyway, I've just confirmed that you installed the patch.
Thank you.

---
Kenichi Handa
address@hidden




reply via email to

[Prev in Thread] Current Thread [Next in Thread]