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.

Sign up for GitHub

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

Jump to bottom

Launch Multiple Windows on Different Desktops #35240

Closed
anish557 opened this issue Sep 27, 2017 · 2 comments
Closed

Launch Multiple Windows on Different Desktops #35240

anish557 opened this issue Sep 27, 2017 · 2 comments
Labels
electron Issues and items related to Electron feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code upstream Issue identified as 'upstream' component related (exists outside of VS Code) workbench-launch Workbench launch
Milestone
Backlog

Comments

@anish557
Copy link

When launching VS code from a new virtual desktop on Windows, you are forced to the virtual desktop that has an active instance of VS code.

I expect that it would render a new window for VS code in the new virtual desktop to let me have different projects open at the same time.
@vscodebot vscodebot bot added the workbench label Sep 27, 2017
@isidorn isidorn assigned bpasero and unassigned isidorn Sep 28, 2017
@bpasero bpasero added electron Issues and items related to Electron upstream Issue identified as 'upstream' component related (exists outside of VS Code) labels Sep 28, 2017
@bpasero bpasero added this to the Backlog milestone Sep 28, 2017
@bpasero bpasero added feature-request Request for new features or functionality and removed workbench labels Nov 12, 2017
@bpasero bpasero removed their assignment Nov 14, 2017
@davidleejy davidleejy mentioned this issue Aug 29, 2018
Closed
@bpasero bpasero added workbench-launch Workbench launch upstream Issue identified as 'upstream' component related (exists outside of VS Code) electron Issues and items related to Electron and removed electron Issues and items related to Electron upstream Issue identified as 'upstream' component related (exists outside of VS Code) labels Sep 19, 2018
@CaptainN CaptainN mentioned this issue Sep 19, 2018
Closed
@CaptainN
Copy link

It seems to work the way this issue requests now - but I'd actually like it to work the way it used to (as I have described in #58978) - is there a way to change it back with a setting?

@chpmrc chpmrc mentioned this issue Nov 29, 2018
Closed
@bpasero bpasero added the *out-of-scope Posted issue is not in scope of VS Code label Oct 10, 2019
@vscodebot
Copy link

vscodebot bot commented Oct 10, 2019

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

@vscodebot vscodebot bot closed this as completed Oct 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
electron Issues and items related to Electron feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code upstream Issue identified as 'upstream' component related (exists outside of VS Code) workbench-launch Workbench launch
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
4 participants
@CaptainN @bpasero @isidorn @anish557