[Top][All Lists]

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

Re: [PATCH] Unconditional quit on SIGUSR2

From: Daniel Colascione
Subject: Re: [PATCH] Unconditional quit on SIGUSR2
Date: Mon, 28 Mar 2011 15:08:39 -0700
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20110303 Thunderbird/3.1.9

On 3/28/2011 3:00 PM, Eli Zaretskii wrote:
I would not recommend anyone to continue using Emacs normally after
interrupting uninterruptible ops.

You're not understanding me.

I'm not talking about interrupting arbitrary code. Instead, I'm talking about interrupting in safe places in situations where quitting is disabled poor UI would otherwise result, not because the code being run is inherently delicate. If interrupting in these places is dangerous, so is inserting an explicit (debug) in the code.

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.

If the user doesn't know when to type C-g, she won't know when to type
"kill PID -USR2", either.

As covered in another branch of this thread, C-g *is* often ambiguous. It's inherently racy when we allow normal quitting of background work. Users would send this signal to Emacs only after noticing an uninterruptable hang. Is that not clear?

reply via email to

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