* Terje Norderhaug [2010-03-22 22:52+0100] writes:
If so, frame-restartable-p should return NIL only when the frame definitely cannot be restarted and T when the frame possibly can be restarted. This makes the current default frame-restartable-p, which always returns NIL, unusable as default for back-ends that have a working restart-frame.
Either back-ends that implement restart-frame also need to implement frame-restartable-p, or the default frame-restartable-p should return T for back-ends that provide a restart-frame function.
With this in place, the backtrace slimefun will more consistently inform the client whether a frame potentially can be restarted or definitely can't be restarted.
Whatever frame-restartable-p returns it doesn't stop the client from calling restart-frame.
Helmut