#475 Save list of most recently opened files after opening a file

open
nobody
None
1
2013-07-08
2013-06-05
Kirill Müller
No

The list of the most recently opened files (File/Open Recent...) should be saved each time a new file is opened, to avoid user disappointment should the operating system or TeXstudio crash.

Only tested with TeXstudio 2.3 on Ubuntu 13.04, could be already implemented in the trunk version.

Discussion

  • Kirill Müller
    Kirill Müller
    2013-06-05

    Same for "Restore previous session" -- should really restore the set of most recently opened files. This should also be saved each time a file is closed.

     
    • Tim Hoffmann
      Tim Hoffmann
      2013-06-05

      Not sure what you mean by that. It uses the same data as Automatically Restore Session at Next Start.

       
  • Tim Hoffmann
    Tim Hoffmann
    2013-06-05

    Crashs should be the exception. If we have them, we have a bigger problem than a lost session. -> Low prio.

     
  • Kirill Müller
    Kirill Müller
    2013-06-30

    That's a matter of perspective. Crashes in TeXstudio are a big problem for the developers who need to fix them, but they are a worse problem for the user, because it interrupts the workflow. Being able to quickly continue just where the interruption occurred is very helpful.

    The 2.6 version doesn't crash on me, but what about a killed process, a crashed X session or power outage?

    For some reasons I didn't receive notification e-mails, that's why my reply took so long.

     
  • You can save them manually with options \ save current settings.

    Or even write a macro to do that (load-file trigger, then simulate click on that menu item)

     
    Last edit: Tim Hoffmann 2013-07-02
  • Kirill Müller
    Kirill Müller
    2013-07-03

    Is the "Save current settings" command so expensive that it cannot be just executed after every open/close action by default? Or does it have effects which prohibit this?

     
  • Tim Hoffmann
    Tim Hoffmann
    2013-07-03

    I don't think it's that expensive, but one has to check for side effects. For example if I save the session with every file opening, "Restore Previous Session" would not work anymore, because the saved session information was overwritten. Of course, one could program around this, but its additional work. There might be more examples like this.

     
  • Kirill Müller
    Kirill Müller
    2013-07-08

    I wasn't aware of the semantics of "Restore previous session". This complicates things.

    One would have to distinguish "auto-save" session information from "properly saved" session information -- the latter is what happens now (clean exit, selection of menu item), the former would be used just in case of a crash. Clean exit and explicit save would also clean any "auto-save" session information, so that the "auto-save" information is used if and only if it exists.

    Do you think this approach would be feasible to implement? Again: Graceful handling of crashes (whatever the reason) is what users just seem to expect nowadays.

     
  • Tim Hoffmann
    Tim Hoffmann
    2013-07-08

    In principle, this would be the way to handle it. It's just that I have a long list of ideas and feature requests. And implementing this means not implementing something else now. Well, given I find time to actively work on new features.

    As a whole, your request is reasonable, and I see your point. I'll leave this request open, but won't promise if and when it will be implemented.

     
  • Kirill Müller
    Kirill Müller
    2013-07-08

    Thank you for considering this.