Feature Request: Krusader restore open tabs on system crash

I’d like to see Krusader restore all open tabs on a system crash, just like all modern browsers do. Maybe even ask first to restore tabs, again like a browser does.

This is something I’ve wished for now for a while, but I’ve been dealing with a nasty bug recently and it’s frustrating when my krusader workspace is reset after I had it just where I needed it. Could it not just keep a file updated as tabs and paths are changed, and then recall this when starting again?

I wasn’t sure if this is the right place to ask for this, so please advise if not.

Thanks for your consideration.

Do you have “restore last session” ticked in Krusader’s settings?

Hi @dzon,
Here are my startup options. I don’t see that exact text, but maybe I’m looking in the wrong place. :crossed_fingers:

Yeah, it’s the first one in the user interface I meant.

In case anyone is tracking this.
https://bugs.kde.org/show_bug.cgi?id=491861

This will be be addressed with change Use KCrash to handle crashes and save settings on crash and signals received (!151) · Merge requests · Utilities / Krusader · GitLab.

Note, that this solution will not work in all cases: If the system suddenly crashes (e.g. due to power failure), there is not chance that the settings can be saved. This will only be done if the Krusader process itself crashes or receives a signal that can be handled (e.g. the TERM signal).

The alternative (complete) solution would be to immediately save the settings after they have been changed, e.g. after changing the folder location in one tab. And this could be a performance problem.
Autosave every x seconds would also be possible, but needs to implemented.

@abikadorov, that’s great news!

While my coding knowledge pretty much ends at scripting in bash, may I as why a simple “state” text file couldn’t be updated continuously as you work? Maybe that requires more overhead than I’m aware of, but my browsers are able to recover all of their tabs even in most catastrophic system crashes.

I personally would be happy to absorb the overhead for the benefit of not losing work, but I completely understand the reasoning of keeping it lean. In which case, could it could be an optional setting?

Regardless, thanks for the work!
I look forward to the update.