>> actually the code to handle sessions for R14.1 has been fully rewritten,
>> although not pushed yet. If you are interested, I can send you a patch
>> with all the current changes and you can test locally. It would be helpful
>> to have additional feedback from you. I have been using the new
>> functionality for about a year and is quite stable. Let me know ;-)
> I build this on jessie some time ago
> dpkg -l | grep kate
> ii kate-plugins-trinity 4:14.1.0-0debian8.0.5+eko1
> amd64 plugins for Kate, the TDE Advanced Text Editor
> ii kate-trinity 4:14.1.0-0debian8.0.5+eko1
> amd64 advanced text editor for TDE
> ii libkate1 0.4.1-4
> amd64 Codec for karaoke and text encapsulation
> Do you mean we are using later version and do not see the problems that are
> discussed here?
> I did not see any difference (IMO) from user perspective.
sorry for the late reply to this (too busy with work, family and trying to fix TDE support for openssl 1.1 in stretch).
Attached is a cumulative patch for tdebase that you can use to preview the new Kate session panel I mentioned before. You can apply the patch again the current main trunk. This will add a new session panel to Kate and rework session support almost entirely. I am actually planning more work on this (to add support for files in sessions as well, making it similar to a mini-project manager) but will probably be delayed to R14.2 or whatever.
!!! Please NOTE the following !!!
- all existing Kate sessions will be imported
- the "default session" is no longer hardwired and actually does not really need to exist any more (it can be renamed/delete)
- after you finish your testing, if you want to go back to the existing Kate (without the new session panel), you will NOT be able to use the session files from Kate-with-the-session-panel. Therefore if you just want to do a test, I recommend you save all you session files (~/.trinity/share/apps/kate/sessions folder) before you use the new Kate.
So far I have used this for about a year (through development) and have not yet pushed the code to the main repo.
Any feedback from you (or anyone else willing to test) would be more than welcome. If positive enough, I will probably push the changes.