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

Allow several settings.json #147911

Closed
turion opened this issue Apr 22, 2022 · 4 comments
Closed

Allow several settings.json #147911

turion opened this issue Apr 22, 2022 · 4 comments
Assignees

Comments

@turion
Copy link

turion commented Apr 22, 2022

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:

  • All *.json files in a predefined folder like ~/.config/Code/User/settings
  • All files matching a regex like settings.*\.json (matching settings.json, settings1.json, settingsReadOnly.json, settingsTeamWide.json, settingsCheckedInToGitRepo.json, etc.)
  • Files given on the command line like 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

  • Software development teams might want to share some of their settings (across multiple workspaces) by checking them into version control. On top, some team members want their own settings.
  • For debugging, one could turn a set of settings on or off by extracting them to a file.
@sandy081
Copy link
Member

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.

@turion
Copy link
Author

turion commented Apr 28, 2022

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?

@sandy081
Copy link
Member

There is a duplicate of this request, please search for existing issues. Thanks.

@turion
Copy link
Author

turion commented May 2, 2022

@github-actions github-actions bot locked and limited conversation to collaborators Jun 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants