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

toggle in/out of zen mode with settings.json file changes active editor #16616

Closed
chrisdias opened this issue Dec 6, 2016 · 6 comments
Closed
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone

Comments

@chrisdias
Copy link
Member

Testing #15647

  • VSCode Version: insiders 1.8.0 a8d5b9
  • OS Version: MacOS

Steps to Reproduce:

  1. open a folder
  2. close all editors
  3. single click on a file to open it in preview mode
  4. open settings.json (CMD+,), now the editor should be replaced
  5. go into zen mode (CMD+K, Z)
  6. exit zen mode (CMD+K, Z)

Result: the last file you had open, before opening the settings file, is now in view. In other words, the settings file is no longer visible. Only seems to happen with settings.json

@chrisdias chrisdias added this to the November 2016 milestone Dec 6, 2016
@isidorn isidorn removed this from the November 2016 milestone Dec 7, 2016
@isidorn isidorn changed the title toggle in/out of zen mode with settings.json file changes active editor explorer.autoReveal bad interaction with preview files Dec 7, 2016
@isidorn
Copy link
Contributor

isidorn commented Dec 7, 2016

As designed. On explorer open we always open the revealed file - there is a setting for this 'explorer.autoReveal'.

So you can get the same behavior if instead of going in and out of zen mode you would show / hide the viewlet.

Though I do agree that your scenario is not nice. But the key problem here is that explorer.autoReveal does not make much sense when an editor is open in preview. Though this is up to ben to decide how to tackle this.

@isidorn isidorn assigned bpasero and unassigned isidorn Dec 7, 2016
@bpasero
Copy link
Member

bpasero commented Dec 7, 2016

This is a consequence of the explorer restoring the last active file when you open it. Another example where we do this is when you jump from Git viewlet back to the explorer we close the diff editor that you likely have open and bring back the file you last worked on. In that scenario I like the flow, however in the described scenario it is not very nice.

Btw the same happens when you open a markdown as preview, close all other editors and hide and show the explorer. The last file you had open restores.

One way to probably fix this is by only restoring the file if it is still open in the editor group.

@bpasero bpasero added this to the January 2017 milestone Dec 7, 2016
@bpasero bpasero added the bug Issue identified by VS Code Team member as probable bug label Dec 7, 2016
@bpasero bpasero changed the title explorer.autoReveal bad interaction with preview files Revisit explorer always restoring last opened file when becoming visible Dec 7, 2016
@bpasero bpasero modified the milestones: Backlog, January 2017 Dec 11, 2016
@bpasero bpasero added debt Code quality issues ux User experience issues and removed bug Issue identified by VS Code Team member as probable bug labels Dec 13, 2016
@bpasero bpasero changed the title Revisit explorer always restoring last opened file when becoming visible toggle in/out of zen mode with settings.json file changes active editor Dec 19, 2016
@bpasero bpasero added bug Issue identified by VS Code Team member as probable bug and removed debt Code quality issues ux User experience issues labels Dec 19, 2016
@bpasero bpasero modified the milestones: January 2017, Backlog Dec 19, 2016
@bpasero
Copy link
Member

bpasero commented Dec 19, 2016

The explorer is now treating the settings and keybindings in the same way as a normal file, so this bug as reported is fixed.

@chrisdias
Copy link
Member Author

LGTM

@isidorn
Copy link
Contributor

isidorn commented Dec 20, 2016

@chrisdias feel free to add a verified label :)

@chrisdias chrisdias added the verified Verification succeeded label Dec 21, 2016
@chrisdias
Copy link
Member Author

@isidorn sorry, added.

@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
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

3 participants