-
Notifications
You must be signed in to change notification settings - Fork 30.7k
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
Allow several settings.json #147911
Comments
It seems you are using VSCodium and this project is VS Code and both are not same. I would request to file issue against VSCodium project. |
Sorry, I accidentally posted the VSCodium paths because I tested whether the issue is there as well. But the issue is about VSCode. I edited the issue description. Can we reopen? |
There is a duplicate of this request, please search for existing issues. Thanks. |
I have searched through >300 issues here: https://github.com/microsoft/vscode/issues?q=is%3Aissue+settings.json+is%3Aopen. I found some related ones: |
Proposed feature
VSCode should not only read the standard
settings.json
, but also additional settings files. I can imagine different ways how to specify these files. For example:*.json
files in a predefined folder like~/.config/Code/User/settings
settings.*\.json
(matchingsettings.json
,settings1.json
,settingsReadOnly.json
,settingsTeamWide.json
,settingsCheckedInToGitRepo.json
, etc.)code --additional-settings=path/to/additional/settings.json
This way, different sets of settings can be specified editor-wide. These would have to be merged with some notion of precedence, similar to how workspace settings are merged with user settings.
Context
I'm trying to improve the VSCode experience on NixOS/Home Manager. There, one configures the editor declaratively, producing a config file that is not writable by the editor. It would be great if there were two settings files, one read-only file produced by Home Manager, and an editor-writable file (the standard
settings.json
).Other use cases
The text was updated successfully, but these errors were encountered: