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

Change 'Closed Workspace' to 'Closed Folder' when we are not using a Workspace #30970

Closed
Tekbr opened this issue Jul 19, 2017 · 0 comments
Closed
Assignees
Labels
workbench-multiroot Multi-root (multiple folders) issues
Milestone

Comments

@Tekbr
Copy link

Tekbr commented Jul 19, 2017

  • VSCode Version: 1.15.0 Insiders ( 3cfa565 , Date 2017-07-17T05:15:33.728Z)
  • OS Version: Windows 10

-- Sorry for the English, I used Google Translator --

Change 'Closed Workspace' to 'Closed Folder' when we are not using a Workspace

From #30608

What's more, why the "Close Folder" option changed "Close Workspace", even though a Workspace has not yet been created? The menu should change only when a workspace was created, right?

menu

Reproduces without extensions: Yes

@bpasero bpasero added this to the July 2017 milestone Jul 19, 2017
@bpasero bpasero self-assigned this Jul 19, 2017
@bpasero bpasero added the workbench-multiroot Multi-root (multiple folders) issues label Jul 19, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
workbench-multiroot Multi-root (multiple folders) issues
Projects
None yet
Development

No branches or pull requests

2 participants