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

Feature request: Allow custom .vscode directory name #41139

Closed
MathiasMagnus opened this issue Jan 4, 2018 · 2 comments
Closed

Feature request: Allow custom .vscode directory name #41139

MathiasMagnus opened this issue Jan 4, 2018 · 2 comments
Labels
config VS Code configuration, set up issues *duplicate Issue identified as a duplicate of another issue(s)

Comments

@MathiasMagnus
Copy link

Suggestion

I would like to request for the ability to set custom folder name to store workspace-specific editor options, canonically stored under a folder named .vscode in ${workspaceRoot}.

Gains

The sheer awesome it would enable now that VS Code opens from within WSL (on Insider builds starting from 17063) is that one could have side-by-side debugging of the very same source tree opened from Windows VS Code with Windows dependencies and WSL with native Linux dependencies.

Current behavior

The problem with the hardcoded ${workspaceRoot}/.vscode is that I cannot set different settings for my Linux and my Windows editor instance which is required to find dependencies (CMake configure params for eg.) on the respective platforms. If I could set .vscode-win and .vscode-wsl respectively, as global settings for the Win and WSL variants, workspace-specific settings would not collide.

@vscodebot vscodebot bot added the workbench label Jan 4, 2018
@bpasero bpasero added config VS Code configuration, set up issues and removed workbench labels Jan 5, 2018
@bpasero bpasero assigned sandy081 and unassigned bpasero Jan 5, 2018
@sandy081
Copy link
Member

sandy081 commented Jan 8, 2018

Duplicate of #851

@sandy081 sandy081 marked this as a duplicate of #851 Jan 8, 2018
@sandy081 sandy081 removed their assignment Jan 8, 2018
@sandy081 sandy081 added the *duplicate Issue identified as a duplicate of another issue(s) label Jan 8, 2018
@vscodebot
Copy link

vscodebot bot commented Jan 8, 2018

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.

Happy Coding!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
config VS Code configuration, set up issues *duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

3 participants