Opening files from unmounted drives wipes their content when drive is mounted

[andersmelin]

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
  • Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
  • Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
  • Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

If, when launching atom, some of the files it tries to open is located on an unmounted drive atom will still create tabs for those files. Those tabs will be blank. If that drive is now mounted atom autosaves those files when they lose focus, leaving them blank.

Steps to Reproduce

1. create a testfile on secondary drive
2. Open the file in atom and write some content
3. Quit atom
4. unmount the drive containing the testfile
5. open atom using the application launcher. Notice the empty tabs
6. Mount the secondary drive
7. Trigger an autosave on the testfile

Expected behavior:
If a file is not accessible atom should not try to display it contents or autosave should be prevented from interfering with that file. Thinking of it, autosave performes it job correctly. Maybe the issue doesnt belong here rather at atom

Actual behavior:
Atom tries to show the files content but since it cannot it displays an empty document which is sensible to autosaves

Reproduces how often: [What percentage of the time does it reproduce?]
100%

Versions

Atom 1.12.7
Autosave 0.23.1
Linux mint 18

Additional Information

In the meantime, use git

[Ben3eeE]

Thanks for taking the time to contribute!

We noticed that this is a duplicate of atom/atom#11797. You may want to subscribe there for updates. We are investigating a fix for a similar issue in atom/atom#15681. You may also want to subscribe there for updates.

Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.

For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.