Olle Olsson writes:
Well, the system told me (before dying) that I could use
to get back whatever-it-was, and I sort of expected that the system on
restart at least would be able to know what buffers/files I might have
For that functionality you need to have a session manager installed
and enabled (I know of at least desktop.el, provided in the XEmacs
packages, and session.el, which should be easily findable by Google).
I'll try to remember to find and fix the message that implies that
session management is built-in.
Actually, I do not know if I had any buffer with 'autosave'.
Then you almost certain do; autosave is a standard feature that you
must explicitly shut off. If XEmacs found no current autosave files,
then you were almost certainly fully saved (to within 300 keystrokes,
including commands), so at most you lose 300 characters of new content.
Any "big" lost changes would either be a "forgotten" deletion
but probably easy to reproduce) or a global search/replace. There are
probably other possibilities, but the principle that any "big" changes
had to involve some automatic, reproducible process, and not your
creativity:-) is valid AFAIK.
Note that autosave works in a lazy fashion as well as using
"recover-session". What I mean is that suppose XEmacs crashes after a
buffer is autosaved but before you explicitly save it. Then the next
few times you work in XEmacs, you forget about that file. But today
you realize you need to work on it. At this point, XEmacs will notice
the autosave file and warn you that you did make unsaved changes to
the file, and offer to revert to the autosaved version (you can even
request a diff to find out if you want the changes or not).
> Actually, we'd prefer you keep reporting bugs. :-) In
> 21.5 is quite stable on Windows AFAIK (I don't use Windows at all).
OK, I will stay with a bleeding-edge version ;-)
XEmacs-Beta mailing list