-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Provide ability to define workspace specific settings from outside the workspace #851
Comments
These things are workspace related settings so they are stored in the workspace folder with the intent to share them to other people (e.g. a launch configuration is typically OS and path independent). You don't have to create workspace settings, there is also user level settings. For launching and tasks however, these files are stored within the workspace. |
I get your point. Indeed making that workspace specific settings live inside the folder makes it shareable. Intelij IDEA stores that meta data either in the workspace folder or in a separate, IDE-owned, folder so that repos are kept clean. Cheers |
@weeblr Here is a nice trick I use for this 😉 Edit Hint: works like a |
Hi alexandru, thanks for the tip. Nice workaround. That doesn't really change anything to the problem however. That folder will still be included in tar balls and such. vscode should just leave the edited code alone. Cheers |
@weeblr fair point |
This should be closed as working as intended |
This would be a nice feature. My project is connected to network drive. This contains folder which are writeable but the root is read only so the vscode has no chance to store the settings file. |
We are planning to support this eventually, stay tuned 👍 |
Any news on this? Have the same issue, need to configure some nice-to-have VSCode tasks but can't do that because it creates a .vscode folder inside my shared workspace/repo where I can't edit the gitignore =( |
Just as a comment, in case someone would not open the mentioned issue (#41139) consider the use case depicted there. My launch.json may look radically different on Windows and inside WSL. In my actual case it's just the type of the C++ debugger and the paths to files in command-line arguments, where in one case it's Duplicating the source tree only to make room for two |
This can be solved by using new
And, settings and debug configurations will be local and no Closing this in favor of using Workspace. |
Hi
When I open a git-controlled folder, and possibly change some settings, then Code creates a .vscode directory directly inside that folder, and stores files such as settings.json or launch.json in it.
That folder either has to be checked in or .ignored, which is OK on repos I control, but not OK on forked repos I want to contribute to for instance, which needs to stay clean.
Can't this data be stored in some Code own data folder?
Cheers
The text was updated successfully, but these errors were encountered: