David Kastrup <[EMAIL PROTECTED]> writes:
> Did you actually read what I wrote above? Bind inhibit-quit to nil in
> the function, and it will be interruptible.
Thanks for your explanation and for the hint, and sorry for the
misunderstanding :-)
--
Michael Cadilhac, a.k.a. Micha [m
Michael Cadilhac <[EMAIL PROTECTED]> writes:
> David Kastrup <[EMAIL PROTECTED]> writes:
>
>> Michael Cadilhac <[EMAIL PROTECTED]> writes:
>>
>>> I've some kind of a freeze in a function being a process filter. My
>>> problem is that I can't figure out where the infinite loop is and
>>>
David Kastrup <[EMAIL PROTECTED]> writes:
> Michael Cadilhac <[EMAIL PROTECTED]> writes:
>
>> Hi !
>>
>> I've some kind of a freeze in a function being a process filter. My
>> problem is that I can't figure out where the infinite loop is and
>> it's a random thing, so I can't use debug
Michael Cadilhac <[EMAIL PROTECTED]> writes:
> Hi !
>
> I've some kind of a freeze in a function being a process filter. My
> problem is that I can't figure out where the infinite loop is and
> it's a random thing, so I can't use debug-on-entry.
>
> This function not being called by
Hi !
I've some kind of a freeze in a function being a process filter. My
problem is that I can't figure out where the infinite loop is and
it's a random thing, so I can't use debug-on-entry.
This function not being called by the user, C-g is not canceling it,
so set debug-on-quit
