Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open Recent yields Save prompt with Hot Exit enabled #17440

Closed
tedhudek opened this issue Dec 17, 2016 · 2 comments
Closed

Open Recent yields Save prompt with Hot Exit enabled #17440

tedhudek opened this issue Dec 17, 2016 · 2 comments
Assignees
Labels
*as-designed Described behavior is as designed workbench-hot-exit Preservation of unsaved changes across restarts

Comments

@tedhudek
Copy link
Member

  • VSCode Version: 1.8.0
  • OS Version: Win10 version 1611

Steps to Reproduce:

  1. Enable Hot Exit. (on by default) Make changes in an editor, don’t save, and close VS Code, it closes with no Save prompt. Restart Code and there’s the editor with unsaved changes. So far, so good.
  2. Now, when you have unsaved changes, use ctrl-R to switch to a recent editor. Save changes prompt appears.

Expected: switches with no save prompt, caching the modified file (same as exiting VS Code)

@bpasero bpasero added the workbench-hot-exit Preservation of unsaved changes across restarts label Dec 17, 2016
@bpasero
Copy link
Member

bpasero commented Dec 17, 2016

I think this works "as-designed" because you are basically giving up the window that contains dirty files and in that case we ask to save. The same happens when closing a window with dirty files that is not the last window.

@Tyriar
Copy link
Member

Tyriar commented Dec 17, 2016

Yes this is as designed, in the future it will be a little more flexible when hot exit triggers (see #15467), in the meantime it's quite conservative.

@Tyriar Tyriar closed this as completed Dec 17, 2016
@Tyriar Tyriar added the *as-designed Described behavior is as designed label Dec 17, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*as-designed Described behavior is as designed workbench-hot-exit Preservation of unsaved changes across restarts
Projects
None yet
Development

No branches or pull requests

3 participants