I would like to be able to have the user code trap the "Emacs interrupts", which are currently being raised by Swank as SIMPLE-ERRORs.

I have defined a USER-INTERRUPT condition which subclasses SIMPLE-ERROR in Swank code, and made it throw that instead.

But, somewhat predictably, trapping SWANK::USER-INTERRUPT from user code did not work, because it seemingly runs the user code in a different thread from the one raising the condition (i.e. the main Swank thread?).

So, the question is, what would be the way to get that which i want with little-to-none injury? (And would such an enhancement be considered useful for Swank in general?)

regards, Samium Gromoff