Re: [PATCH] Unconditional quit on SIGUSR2

[Lennart Borgman]

On Mon, Mar 28, 2011 at 9:49 PM, Daniel Colascione
<address@hidden> wrote:
>>
>> If it is safe to interrupt font-lock with the method used by your
>> patch, it should be safe to enable quitting when redisplay calls
>> font-lock, right?  So maybe we should simply enable quite when
>> redisplay calls font-lock and disable it when font-lock returns back
>> to redisplay code which called it.  Then C-g will be able to interrupt
>> it.  Would that solve the problem with font-lock that gets stuck?
>
> It would solve that problem but introduce another: users have no way of
> knowing went font-lock happens.  Innocently typing C-g at the wrong time can
> terminate font lock and leave parts of the buffer unfontified.  It's
> inherently racy.  We need an alternate mechanism that is not as easy to
> trigger.  Signals provide such a mechanism.

But can't that be taken care of by letting font lock run again?