Stefan Krusche wrote:
- 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.
- 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)
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.
Am Mittwoch 21 Dezember 2016 schrieb Dave Lers:
Stefan Krusche wrote:
- 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.
- 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 ~/.trinity/share/apps/kate/sessions/default.katesession
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.
ACK
Stefan
Stefan Krusche wrote:
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.
This only happens when startup is set to new session. A new session is an unnamed session and cannot be saved. In this case you have to switch to the default (or a named) session and then make your changes.
I believe the startup default is the select session dialog which will create default.katesession if it doesn't exist. Same goes for the last used session startup option.
In all cases, only changes made to the currently open named session will be saved and they will only be saved to that named katesession file. To prevent weirdness, change all sessions using the actual menu settings, because Kate applies the startup session config to all sessions opened from the Sessions menu.
would not let me save the freshly opened session, but popped up a
That happens when there is still no file ~/.trinity/share/apps/kate/sessions/default.katesession
It happens any time you're using a new/unnamed session
On 2016-12-21 16:28:10 Dave Lers wrote:
In all cases, only changes made to the currently open named session will be saved and they will only be saved to that named katesession file. To prevent weirdness, change all sessions using the actual menu settings, because Kate applies the startup session config to all sessions opened from the Sessions menu.
But that didn't work for me either. 1) Delete .trinity/share/apps/kate 2) Open Kate 3) Sessions -> Open Shows two sessions: Default Session 0 Session (05:46:34 PM) 1 4) Select Session (05:46:34 PM), click Open 5) Window -> Tool View -> Hide Documents 6) Sessions -> Save 7) Close Kate 8) Open Kate -- Document view persists. :-(
Leslie
Leslie Turriff wrote:
On 2016-12-21 16:28:10 Dave Lers wrote:
In all cases, only changes made to the currently open named session will be saved and they will only be saved to that named katesession file.
I decided to repeat your steps from top to bottom using your 'choose session' startup setting.
- Delete .trinity/share/apps/kate
I had to open default session and save as Session (05:46:34 PM) so I could choose it later.
- Open Kate
- Sessions -> Open Shows two sessions: Default Session 0 Session (05:46:34 PM) 1
- Select Session (05:46:34 PM), click Open
- Window -> Tool View -> Hide Documents
- Sessions -> Save
- Close Kate
- Open Kate -- Document view persists. :-(
Only when the Default Session is chosen at startup, NOT when "Session (05:46:34 PM)" is chosen at startup.
Dave Lers wrote:
- Open Kate -- Document view persists. :-(
Only when the Default Session is chosen at startup, NOT when "Session (05:46:34 PM)" is chosen at startup.
Any option other than "Session (05:46:34 PM)" will show the Document pane, because it is the only option that has been configured not to show it, e.g. new session will show it because default session has not been configured not to show it.
On 2016-12-21 19:42:24 Dave Lers wrote:
Dave Lers wrote:
- Open Kate -- Document view persists. :-(
Only when the Default Session is chosen at startup, NOT when "Session (05:46:34 PM)" is chosen at startup.
Any option other than "Session (05:46:34 PM)" will show the Document pane, because it is the only option that has been configured not to show it, e.g. new session will show it because default session has not been configured not to show it.
But Session (05:46:34 PM) was the one I selected, and it DID show the Document pane.
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On 2016-12-21 15:17:15 Stefan Krusche wrote:
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.
But that doesn't work for me. 1) Delete .trinity/share/apps/kate 2) Open Kate 3) Sessions -> Open -> Default Session 4) Window -> Tool Views -> Hide Documents 5) Sessions -> Save 6) Close Kate 7) Open Kate -- Document view persists. :-(
Leslie
Leslie Turriff wrote:
On 2016-12-21 15:17:15 Stefan Krusche wrote:
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.
But that doesn't work for me.
- Delete .trinity/share/apps/kate
- Open Kate
- Sessions -> Open -> Default Session
- Window -> Tool Views -> Hide Documents
- Sessions -> Save
- Close Kate
- Open Kate -- Document view persists. :-(
Leslie
Hi, is this discussion some kind of joke? What linux variant and TDE version are you using?
I did fresh install of wheezy and TDE 14.0.4 2days ago.
1) Delete .trinity/share/apps/kate 2) Open Kate 3) Sessions -> Open -> Default Session 4) Window -> Tool Views -> Hide Documents 5) Sessions -> Save 6) Close Kate 7) Open Kate -- Document view is hidden
same effect in 4) with pressing documents tab to hide the view.
I do not see any problem here. In jessie I use with partially TDE 14.1.0 I also do not see a problem.
Can you try this in a different account (fresh) and report back, please?
regards
On 2016-12-22 17:29:43 deloptes wrote:
Leslie Turriff wrote:
On 2016-12-21 15:17:15 Stefan Krusche wrote:
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.
But that doesn't work for me.
- Delete .trinity/share/apps/kate
- Open Kate
- Sessions -> Open -> Default Session
- Window -> Tool Views -> Hide Documents
- Sessions -> Save
- Close Kate
- Open Kate -- Document view persists. :-(
Leslie
Hi, is this discussion some kind of joke?
No joke.
What linux variant and TDE version are you using?
TDE R14.0.4, Kate 2.5.4, on OpenSuSE Leap 41.1 x86_64.
I did fresh install of wheezy and TDE 14.0.4 2days ago.
Delete .trinity/share/apps/kateOpen KateSessions -> Open -> Default SessionWindow -> Tool Views -> Hide DocumentsSessions -> SaveClose KateOpen Kate -- Document view is hiddensame effect in 4) with pressing documents tab to hide the view.
I do not see any problem here. In jessie I use with partially TDE 14.1.0 I also do not see a problem.
Can you try this in a different account (fresh) and report back, please?
Okay.
regards
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On 2016-12-22 17:29:43 deloptes wrote:
Can you try this in a different account (fresh) and report back, please?
With a new account, configured via the TDE wizard with only a change to the classic look, Kate works the way everyone has described it. With Settings -> Sessons -> Open last saved sesson, Save Session, the changes are remembered. I also tried Kate on another account where Kate isn't used, and it also behaves correctly; that account, like the one I use most, predates installation of Trinity. So it appears that there is something in my most-used account that is interfering with Kate's ability to remember its session settings, which might or might not have been carried over from KDE3, or come from Gnome, or XFCE.
Leslie
Leslie Turriff wrote:
On 2016-12-22 17:29:43 deloptes wrote:
Can you try this in a different account (fresh) and report back, please?
With a new account, configured via the TDE wizard with only a change to the classic look, Kate works the way everyone has described it. With Settings -> Sessons -> Open last saved sesson, Save Session, the changes are remembered. I also tried Kate on another account where Kate isn't used, and it also behaves correctly; that account, like the one I use most, predates installation of Trinity. So it appears that there is something in my most-used account that is interfering with Kate's ability to remember its session settings, which might or might not have been carried over from KDE3, or come from Gnome, or XFCE.
Leslie
Thanks so it was quite a bit of a progress. Now we see it is a local problem and not a bug in the app.
I see here also file - might be relevant .trinity/share/config/session/kate* on my system it is from 2015 ... seems very old, but the default session in ./share/apps/kate/sessions/ is also from 2015. I recall I stopped using it as it was having some issues I do not recall ATM. I started using custom sessions related to group of tasks/documents
You can also try diff -r old/new .trinity dir
I checked quickly here
/.trinity$ grep -r Kate-MDI-ToolView-kate_filelist-Visible . ./share/config/session/kate_10e1d0db73000144560300200000045480037_1445807548_826952:Kate-MDI-ToolView-kate_filelist-Visible=true ./share/apps/kate/sessions/9f45c5b6cf8fab93dd47e270908d519f.katesession:Kate-MDI-ToolView-kate_filelist-Visible=true ./share/apps/kate/sessions/82be5fd7f9f81774d6efb8c8a1b053f0.katesession:Kate-MDI-ToolView-kate_filelist-Visible=true ./share/apps/kate/sessions/86240bcd71ceccd04eb82ef560023676.katesession:Kate-MDI-ToolView-kate_filelist-Visible=true ./share/apps/kate/sessions/361b21bd8228704d89e897c416036477.katesession:Kate-MDI-ToolView-kate_filelist-Visible=false ./share/apps/kate/sessions/8ce2069f091c5ddee6eb33956b27ee0b.katesession:Kate-MDI-ToolView-kate_filelist-Visible=true ./share/apps/kate/sessions/e044101a99db7bf8b0e953cff4063798.katesession:Kate-MDI-ToolView-kate_filelist-Visible=true ./share/apps/kate/sessions/default.katesession:Kate-MDI-ToolView-kate_filelist-Visible=true ./share/apps/kate/sessions/ce927b51474626a3ece5604b117e740d.katesession:Kate-MDI-ToolView-kate_filelist-Visible=true
regards
On 2016-12-23 03:09:28 deloptes wrote:
Thanks so it was quite a bit of a progress. Now we see it is a local problem and not a bug in the app.
I see here also file - might be relevant .trinity/share/config/session/kate* on my system it is from 2015 ... seems very old, but the default session in ./share/apps/kate/sessions/ is also from 2015. I recall I stopped using it as it was having some issues I do not recall ATM. I started using custom sessions related to group of tasks/documents
You can also try diff -r old/new .trinity dir
I checked quickly here
/.trinity$ grep -r Kate-MDI-ToolView-kate_filelist-Visible . ./share/config/session/kate_10e1d0db73000144560300200000045480037_144580754 8_826952:Kate-MDI-ToolView-kate_filelist-Visible=true ./share/apps/kate/sessions/9f45c5b6cf8fab93dd47e270908d519f.katesession:Kat e-MDI-ToolView-kate_filelist-Visible=true ./share/apps/kate/sessions/82be5fd7f9f81774d6efb8c8a1b053f0.katesession:Kat e-MDI-ToolView-kate_filelist-Visible=true ./share/apps/kate/sessions/86240bcd71ceccd04eb82ef560023676.katesession:Kat e-MDI-ToolView-kate_filelist-Visible=true ./share/apps/kate/sessions/361b21bd8228704d89e897c416036477.katesession:Kat e-MDI-ToolView-kate_filelist-Visible=false ./share/apps/kate/sessions/8ce2069f091c5ddee6eb33956b27ee0b.katesession:Kat e-MDI-ToolView-kate_filelist-Visible=true ./share/apps/kate/sessions/e044101a99db7bf8b0e953cff4063798.katesession:Kat e-MDI-ToolView-kate_filelist-Visible=true ./share/apps/kate/sessions/default.katesession:Kate-MDI-ToolView-kate_filel ist-Visible=true ./share/apps/kate/sessions/ce927b51474626a3ece5604b117e740d.katesession:Kat e-MDI-ToolView-kate_filelist-Visible=true
Okay. I didn't know that the same settings appear in two different files. (Why is that?)
I did these steps: 1) rm ~/.trinity/share/apps/kate 2) rm ~/.trinity/share/config/kate_* 3) rm ~/.trinity/share/config/katerc 4) opened Kate, which asked to select a session; chose Default Session 5) Window -> Tool Views -> Hide Documents 6) Window -> Tool Views -> Hide Sidebars 7) closed Kate 8) reopened Kate; Success!
So apparently one has to remove at least the first two configuration items (not sure about katerc) to ensure that the tool views settings are properly accepted. I see now that Kate did not recreate ~/.trinity/share/config/kate_*, and only default.session exists in ~/.trinity/share/apps/kate/sessions.
Thank you all for helping clarify how this works.
Leslie
Leslie Turriff wrote:
Okay. I didn't know that the same settings appear in two different files. (Why is that?)
what do you mean it appears in two different files?
I did these steps: 1) rm ~/.trinity/share/apps/kate
here in sessions are the session settings stored
2) rm ~/.trinity/share/config/kate_* 3) rm ~/.trinity/share/config/katerc
the two above are not really relevant - are they?
4) opened Kate, which asked to select a session; chose Default Session 5) Window -> Tool Views -> Hide Documents 6) Window -> Tool Views -> Hide Sidebars
This should not have to do anything with the documents view. It hides the whole of the side bar ... well if you prefer, be it
7) closed Kate 8) reopened Kate; Success!
cool
So apparently one has to remove at least the first two configuration items (not sure about katerc) to ensure that the tool views settings are properly accepted. I see now that Kate did not recreate ~/.trinity/share/config/kate_*, and only default.session exists in ~/.trinity/share/apps/kate/sessions.
in config ( ~/.trinity/share/config/ ) are the configuration files related to the application. in app/kate/sessions/ are the files related to the sessions.
It might have been a setting in your files that was moved to the session settings and thus was overwriting the session setting, while you were not able to change it, because the version we use now writes to the session setting ... just a theory.
regards
On 2016-12-23 16:48:03 deloptes wrote:
Okay. I didn't know that the same settings appear in two different files. (Why is that?)
what do you mean it appears in two different files?
I deleted the offending file, so can't show you, but the ~/.trinity/share/config/kate_* file had part of what's in ~/.trinity/share/apps/kate/sessions/default.katesession; specifically the [MainWinow0] section, which contains the offending Kate-MDI-Sidebar-Visible= parameter.
Leslie
Leslie Turriff wrote:
On 2016-12-23 16:48:03 deloptes wrote:
Okay. I didn't know that the same settings appear in two different files. (Why is that?)
what do you mean it appears in two different files?
I deleted the offending file, so can't show you, but the ~/.trinity/share/config/kate_* file had part of what's in ~/.trinity/share/apps/kate/sessions/default.katesession; specifically the [MainWinow0] section, which contains the offending [Kate-MDI-Sidebar-Visible= parameter.
Leslie
Ah ok, so it speaks for my theory. Anyway, now you've solved it.
regards
Attached is an image of the offending file, ~/.trinity/share/config/session/kate_101ca1791c8170000148184228100000115160016_1481844698_659863, which I cut/pasted from less, for your perusal. I have no idea how it came to exist, since apparently Kate doesn't create such files itself?
Leslie
On 2016-12-24 02:58:55 deloptes wrote:
Leslie Turriff wrote:
On 2016-12-23 16:48:03 deloptes wrote:
Okay. I didn't know that the same settings appear in two different files. (Why is that?)
what do you mean it appears in two different files?
I deleted the offending file, so can't show you, but the ~/.trinity/share/config/kate_* file had part of what's in ~/.trinity/share/apps/kate/sessions/default.katesession; specifically the [MainWinow0] section, which contains the offending [Kate-MDI-Sidebar-Visible= parameter.
Leslie
Ah ok, so it speaks for my theory. Anyway, now you've solved it.
regards
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-
Dave Lers -
deloptes -
Leslie Turriff -
Stefan Krusche