Opened 17 years ago

Closed 17 years ago

Last modified 11 years ago

#131 closed enhancement (fixed)

Add preference setting for interrupt command

Reported by: David Aspinall Owned by: David Aspinall
Priority: minor Milestone:
Component: 1:pg-eclipse Keywords:
Cc:

Description

This is prover specific and (in the case of Isabelle), unfortunately hard to determine. Code currently has "killall -2 HOL" hardwired. This should be moved to a prover preference setting (near Use PGIP interrupts)

Attachments (1)

mylyn-context.zip (5.3 KB) - added by David Aspinall 17 years ago.
mylyn/context/zip

Download all attachments as: .zip

Change History (5)

comment:1 Changed 17 years ago by David Aspinall

Owner: changed from David Aspinall to Graham Dutton

comment:2 Changed 17 years ago by David Aspinall

Owner: changed from Graham Dutton to David Aspinall

A message from Makarius on the Isabelle mailing list suggests a way through here. Ideally it would be better *not* to have a per-prover setting.

Peeking at comint.el reveals that emacs signals the whole process group of 
the controlling pty here.  I've managed to imitate this behaviour in the 
shell using kill with negated PID like this:

  kill -INT -- -4711

Also note that the Isabelle/Isar toplevel ignores any INT signals unless 
it actually runs a command.  To test kills more easily you may use the raw 
ML toplevel, which reports something like ``Compilation interrupted''.

comment:3 Changed 17 years ago by David Aspinall

Resolution: fixed
Status: newclosed

Fixed by adding preference for interrupt OS command after all. Seems to be no way to signal sub-processes in Java. Best solution may be to add wrappers to provers to intercept <interruptprover> command.

Changed 17 years ago by David Aspinall

Attachment: mylyn-context.zip added

mylyn/context/zip

comment:4 Changed 11 years ago by David Aspinall

Milestone: PG-Eclipse-1.0.6

Milestone PG-Eclipse-1.0.6 deleted

Note: See TracTickets for help on using tickets.