Unexpected behavior when removing a folder with pending file changes.

[pthiess]

Steps to reproduce

1. Create a new folder (Untitled-1) and a new file (Untitled-2) within the folder
2. Start editing untitled-2, do not save
   

3.Delete the folder Untitled-1

1. Choose to keep changes in editor
2. Quit Brackets
3. When prompted to save changes choose
   
4. Choose Ok. Quit is interrupted.
5. Try step 6 again and choose not to save.
6. Open Brackets again (note: this didn't reproduce every time, so ignore the file name)
   

Issues

• Unsaved files in deleted folders are attempt to be saved as is instead of utilizing to identify the location
• Unsaved files are somehow cached in some scenarios and cause errors when Brackets is started

Expected behaviour

Path names are checked and is being used instead in the above scenario.
Even if an attempt to save hasn't worked and the stream is recycled Brackets doesn't attempt to open unsaved files.

[peterflynn]

@pthiess I think this is a dupe of #4760. The last part (step 6) wasn't reported before, so if you close this we should mention that additional symptom in the original bug.

[peterflynn]

Reviewed - closing as duplicate, will update #4760 with the details from here