Steps to reproduce: Open Kate to a fresh unnamed session. Open a few files (or not). Click Sessions > Save Session. Observed: Nothing happens. The current session is not saved since it is unnamed. (If we are in a named session it does work as expected.) Desired: In an unnamed session, clicking on Save Session should ask for a session name. IOW, it should behave the same as Save Session As. This is the same as doing Ctrl+S or File>Save when an unnamed document is open.
*** Bug 342057 has been marked as a duplicate of this bug. ***
This get's a little bit tricky. There actualy is a functionality behind saving an unnamed session. It's currently the only way to configure plugins and view layouts for unnamed session. But yeah, it's not clear from the first look. UX is not easy:)
*** Bug 362864 has been marked as a duplicate of this bug. ***
*** Bug 268913 has been marked as a duplicate of this bug. ***
Git commit dd54d50732158581aa97cce36fc170025b71be96 by Christoph Cullmann, on behalf of Ahmad Samir. Committed on 02/03/2019 at 15:15. Pushed by cullmann into branch 'master'. Make "Save Session" action ask for a name for anonymous sessions Summary: When invoking "Save Session", kate should ask for a session name if the session is anonymous, i.e. the same behaviour when using saving a a new file/unnamed document. FIXED-IN: 19.04.0 Test Plan: Opening a kate instance with a new/anonymous session and invoking "Save Session" should ask the user to enter a name for the session. Reviewers: #kate, cullmann, dhaumann Reviewed By: #kate, cullmann Subscribers: ngraham, kwrite-devel, #kate Tags: #kate Differential Revision: https://phabricator.kde.org/D19017 M +5 -1 kate/session/katesessionmanager.cpp https://commits.kde.org/kate/dd54d50732158581aa97cce36fc170025b71be96