Version: (using KDE KDE 3.5.1) Installed from: Mandriva RPMs OS: Linux If you open Kate with the default session, and open several files, and then cause X to crash (CTRL-ALT-BKSP will do nicely), the session changes are lost. When you re-launch Kate, it will have the session info as of the last start, but none of the unsaved changes. Since these changes *are* saved automatically during any sort of controlled shutdown (e.g. window close), they should probably be saved as they occur. Adding and deleting files in the session isn't such a high-frequency activity that it would pose an undue burden.
As you may have noticed, the settings are saved during a clean shutdown. If you don't close Kate cleanly, you don't get settings saved. In fact, that is true for most KDE applications. If your system or your X crashes, or if you have a power failure, you will reload at mostly the same settings as you had the last time you logged on.
Well, yes, I know all that. That's why I opened the bug with the description I gave. Are you saying that the behavior I request isn't a desirable one for the product ? Surely, the cost of rewriting the settings when file is added or closed is fairly trivial ?
I agree, we should provide an option for autosaving sessions, which would just save any session relevant change immediately.
I don't know why this was set to grave. It does not *cause* data loss, and compared to actual loss of the text files themselves I'd say it's not exactly critical data, either. (I still agree it should be guarded against by saving session info more often, automatically.) Also, this is a dupe of bug #107710 . *** This bug has been marked as a duplicate of 107710 ***