Sessions is how Kate lets you keep more than one list of files and GUI configuration around. You can have as many named sessions as you want, and you can use unnamed or anonymous sessions for files you want to use only once. Currently Kate can save the list of open files, and the general window configuration in the session, future versions of Kate may add more features that can be saved in sessions. With the introduction of sessions, Kate also allows you to open any number of instances of the application instead of just one as it used to do as the default behavior.
Sessions are supported in tree areas:
Command line options that lets you select and start sessions when launching kate from the command line.
The Sessions menu that lets you switch, save, start and manage your sessions
Configuration options that lets you decide how sessions generally should behave.
When you get used to using sessions you will hopefully see that they provide a very simple and efficient tool for working in different areas. However, if you prefer the old Kate behavior (one instance opens all files), you can easily achieve that by following this simple strategy:
Make kate allways start with the --use
parameter by adding that to the command in the application preferences,
and additionally using a shell alias.
Configure Kate to load the last used session at startup.
Configure Kate to save the file list when closing a session.
Load the default session once
Would you like to make a comment or contribute an update to this page?
Send feedback to the KDE Docs Team