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

Saving a file no longer keeps it open #41314

Closed
Brocco opened this issue Jan 8, 2018 · 3 comments
Closed

Saving a file no longer keeps it open #41314

Brocco opened this issue Jan 8, 2018 · 3 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded workbench-editors Managing of editor widgets in workbench window
Milestone

Comments

@Brocco
Copy link

Brocco commented Jan 8, 2018

  • VSCode Version: 1.20.0-insider (b811600)
  • OS Version: macOS High Sierra 10.13.2

Steps to Reproduce:

  1. Open a file (A)
  2. Make no changes
  3. Save file (cmd + s)
  4. Open another file (B)

expected: B opens and A remains open
actual: B opens and A closes
Note: this is a change to previous behavior

Does this issue occur when all extensions are disabled?: Yes/No
Yes, still occurs

@vscodebot vscodebot bot added the insiders label Jan 8, 2018
@vscodebot vscodebot bot added the workbench label Jan 8, 2018
@bpasero bpasero added bug Issue identified by VS Code Team member as probable bug workbench-editors Managing of editor widgets in workbench window and removed workbench labels Jan 9, 2018
@bpasero bpasero added this to the December 2017/January 2018 milestone Jan 9, 2018
@bpasero bpasero assigned isidorn and unassigned bpasero Jan 9, 2018
@bpasero
Copy link
Member

bpasero commented Jan 9, 2018

@isidorn this looks like a regression from your refactoring. in here we pin the editor if no resource is provided but it looks like the resource is an empty object that is passed in. this seems to be originating from this weird rule (that I never understood) in keybindings service.

I fear all the commands you introduced need a check for URI.isURI() to work properly now. I would do this check from the commands though and not from the various helper functions because otherwise it is totally unclear why this check is needed in the first place :-/

@isidorn isidorn closed this as completed in dbcae0f Jan 9, 2018
@Brocco
Copy link
Author

Brocco commented Jan 19, 2018

FYI, this seems to have regressed again, should I open a new issue?

@isidorn
Copy link
Contributor

isidorn commented Jan 22, 2018

@Brocco thanks for letting us know. However this was fixed on friday and should appear in the next insiders release.
Here's that issue #41841

@bpasero bpasero added the verified Verification succeeded label Feb 1, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Feb 23, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded workbench-editors Managing of editor widgets in workbench window
Projects
None yet
Development

No branches or pull requests

3 participants