Message: previous - next
Month: December 2016

Re: [trinity-users] Re: Kate can't remember to 'Hide Documents'r

From: Stefan Krusche <linux@...>
Date: Wed, 21 Dec 2016 22:17:15 +0100
Am Mittwoch 21 Dezember 2016 schrieb Dave Lers:
> Stefan Krusche wrote:
> > 2) close the documents list (and/or side bar), save the session.
> >   There is only "Default session", so the running session, which
> > is the default session, will be saved as default.session in
> > kate/sessions/ (would be saved in default.session anyway, but
> > without your changes)
> Making the initial tool view changes to the default session may be the
> key. While I already had a default session, that is where I made the
> initial changes and I have not had any issues with the memory loss
> others are experiencing.

I found this:

1.) "save session" is already set as default option

2.) When you start kate the first time with an empty or no config directory at 
all. As Michele said kate starts with a "hard-wired" default session.

3.) It does not work like I said before in 2) (see above). When I simply change 
the interface to not show docs list and close kate, it does not get saved. The 
created config/sessions directory stays empty just like Leslie experienced. 
No "default.katesession" file there. I think this is a bug. Users would expect 
a changed default session to be saved in user config dir.

As a workaround you can make kate save a default.katesession file. When you 
open "Default Session" after you started kate first time etc. then it _will_ be 
saved as default.katesession file with the applied changes.

Otherwise, when the file ~/.trinity/share/apps/kate/sessions/default.katesession 
already exists there seems to be no problem.

> > 3) next time you start kate, it will find default.session with your
> > saved changes concerning the view of docs list/side bar.
> >
> > BUT: still strange is, that the second time I tried that, kate
> > would not let me save the freshly opened session, but popped up a
> > dialog to enter a name for the session to save. I then "opened"
> > from within kate "Default session" (the only one in the list)

That happens when there is still no file

> I didn't have this issue because I had Kate configured to save
> sessions on exit. I can confirm that manually saving the default
> session (when it is the only session) can only be done after selecting
> it from the Sessions menu.