I think that XEmacs 21.2 isn't autosaving when it's signalled. Will someone else please test this? I discovered it when an unmapped XEmacs' gnuserv died. With or without gpm, and with or without -unmapped, I get the same thing. Edit ~/blah, save it, edit some more, don't save, then send a sigHUP to XEmacs and make it exit. It says it autosaved, but when I start it up again and do `M-x recover-session', it doesn't work. "blah" wasn't autosaved as advertised, as far as I can tell. ? <offtopic> I began a more detailed bug report last night, then had a system lockup... I'd hibernated my laptop for the night, and turned it on this morning. All of the backed up cron jobs fired off at once, and rather than wait for the hour or more of thrashing, I power cycled the thing, and lost the bug report I'd started. Grrr. I fixed that; serialized all my cron scripts with a `source' include that uses the procmail lockfile program and a trap to cleanup the lockfile. That's what I learned today.