Spyder: Newly created file stored on exit is not opened on next start

[oscargus]

Issue Report Checklist

• [x] Searched the issues page for similar reports
• [x] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
• [x] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
• [x] Tried basic troubleshooting (if a bug/error)
  
  
  
  • [x] Restarted Spyder
  
  
  • [ ] Reset preferences with spyder --reset
  
  
  • [x] Reinstalled the latest version of Anaconda
  
  
  • [ ] Tried the other applicable steps from the Troubleshooting Guide
  
  
• [x] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description

When a new file is saved the first time upon exit, it is not opened the next time Spyder is opened. Holds for both master and 3.3.4. (Not a major issue, but you notice these things when you develop and open/close Spyder a lot...)

Probably the storing of open files happens before any edited files checks are done.

What steps reproduce the problem?

1. Create a new file and edit a bit in it
2. Close Spyder and upon request, save the file using a new file name
3. Start Spyder again

What is the expected output? What do you see instead?

That the new file should be open. It can be argued if it should be active or not (if it wasn't active), but I think at least it should open.

Versions

• Spyder version: 4.0.0.dev0 (and 3.3.4)
• Python version: 3.7.3 64-bit
• Qt version: 5.9.6
• PyQt version: 5.9.2
• Operating System name/version: Windows 10

Dependencies

pygments >=2.0    :  2.4.2 (OK)
qdarkstyle >=2.6.4:  2.7 (OK)
sphinx >=0.6.6    :  2.1.0 (OK)
pyls >=0.27.0     :  0.27.0 (OK)
nbconvert >=4.0   :  5.5.0 (OK)
pandas >=0.13.1   :  0.24.2 (OK)
numpy >=1.7       :  1.16.4 (OK)
sympy >=0.7.3     :  1.4 (OK)
cython >=0.21     :  0.29.10 (OK)
qtconsole >=4.5.0 :  4.5.1 (OK)
IPython >=4.0     :  7.5.0 (OK)
matplotlib >=2.0.0:  3.1.0 (OK)
pylint >=0.25     :  2.3.1 (OK)

[ccordoba12]

@oscargus, do you plan to solve this issue? If that's the case (for this and future problems you find), there's no need for you to first open an issue about it. Instead, please push directly your PR.

[oscargus]

Hard to say. The main reason for opening an issue is not that I will get to close it shortly after (I typically leave the same type of comments of not having to open an issue to motivate a PR in e.g. SymPy). Even though I understand that it may look like it, considering the activity in the last few days. Typically, I just wander away browsing the code and sometimes I see an obvious fix for it, although it is not really planned for. But I haven't got a PR ready (nor have browsed the code) when opening an issue.

So, no, I do not have any immediate plans for it. Which doesn't mean that it won't happen...

[jnsebgosselin]

@ccordoba12 I know this part of the code well, I think I can take care of that one. Thanks for the bug report @oscargus.

[goanpeca]

@jnsebgosselin if you could give us a hand with this one, that would be great!

Thanks :-)