Kate saving new file as .local/share/kate/stash/%7C.katesession/Document 52:13

For the past couple of days, a new unnamed file in Kate, when saved becomes
.local/share/kate/stash/%7C.katesession/Document 52
Is this a bug introduced by a recent update or can it be fixed?

I can confirm this. Not sure how long it’s actually been like this but at least in my case, sessions have been messed up as well.

Not sure about a “fix” apart from just changing the path.

Looks like something similar has been reported, but not yet resolved.

https://bugs.kde.org/show_bug.cgi?id=497478

2 Likes

I’m just curious as to why you would save a unnamed file?

1 Like

It’s actually changing unsaved files’ names to “Document 09” etc. unless you manually save before switching tabs.

I have 11 documents in my session, but it now only loads 3 of them (none at first). Won’t open the other 8 when restoring the session.

From the report @Takakage referenced (see above):

If we are to take that comment at face value, unchecking both of the following Kate Session options works around the issue;

  • Newly-created unsaved files
  • Files with unsaved changes
2 Likes

In order to name it. Normally with an unnamed file one hits the ‘save’ button or ctrl/s and specifies a name and location. the ‘save as’ might be better as an interim.

That seems to work for me too.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.