Hi,
On Thu, 2006-06-08 at 09:36 +0100, Toby Speight wrote:
Sven Well, in theory it could catch the signal and clean up before it
Sven exits.
No, SIGKILL can't be caught by a process.
The plug-in receives a QUIT message on the wire before it is being
killed. Probably not trivial to do the
0 In article [EMAIL PROTECTED],
0 Sven Neumann URL:mailto:[EMAIL PROTECTED] (Sven) wrote:
Sven On Wed, 2006-06-07 at 17:36 +0100, Toby Speight wrote:
While we're on this subject - obviously the plug-in process has no
chance to clear up if it's killed outright,
Sven Well, in theory it could
0 In article [EMAIL PROTECTED],
0 Nathan Summers URL:mailto:[EMAIL PROTECTED] (Nathan) wrote:
Nathan Cancelling a plugin kills it unconditionally. It's been a
Nathan few months since I looked at that code, but I'm fairly sure
Nathan that there is no way for a plug-in to catch that it's been
Hi,
On Wed, 2006-06-07 at 17:36 +0100, Toby Speight wrote:
While we're on this subject - obviously the plug-in process has no
chance to clear up if it's killed outright,
Well, in theory it could catch the signal and clean up before it exits.
so what happens to e.g. undo stack in this case?
On Wed, 2006-06-07 at 19:54 +0200, Sven Neumann wrote:
Hi,
On Wed, 2006-06-07 at 17:36 +0100, Toby Speight wrote:
While we're on this subject - obviously the plug-in process has no
chance to clear up if it's killed outright,
Well, in theory it could catch the signal and clean up
