https://bugs.kde.org/show_bug.cgi?id=416137
--- Comment #1 from Raphael Rosch <kdeb...@insaner.com> --- Further testing reveals that the problem isn't with the "close other" feature, but rather that closing the session triggers its automatic save ( KateSessionManager::saveActiveSession -> KateSessionManager::saveSessionTo ), which is a departure from how it used to handle the situation. kate should not overwrite the current session when closing the application, but instead, if an autosave is desired (optimally, this should be a user-selectable option) it should save to a designated /different/ file (say, "autobak.katesession") or to a "backup" copy of the session (ie, if using "my session", it should create a "my session-autobak" session or something like that). I'm going to see if I can whip up a quick patch, if at least for those who want a parting point to work on this. -- You are receiving this mail because: You are watching all bug changes.
