kpc00@JUTS.ccc.amdahl.com (kpc) (08/22/90)
There are circumstances, such as certain bugs or bad redirections, where emacs will end up in the background or someplace else, running or stopped but inaccessible except through signals. How about defining a sequence of signals that, when sent to emacs correctly, would cause it to save the window configuration and all files in a safe location separate from that of the original files? Does anybody like this idea? How would one go about it, assuming that it can be done in elisp. (elisp has encouraged me to become ever more snobbish about the HLL concept :-).) I do hope that elisp allows signal processing. Does it? (I don't have the elisp manual or even ftp/uucp at this point, and apropos is not giving encouraging results.) P.S. A more fancy equivalent would be some kind of inter-process communication that would allow the errant emacs to be a server and the recovery program to be a client. The recovery program would send the sequence and then hook up to the errant emacs, allowing you to recover in any way that you want. This should not depend on X or any other non-universal IPC, however. -- Neither representing any company nor, necessarily, myself.