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 import of additional settings files to the main user settings.json #80360

Closed
slavdok opened this issue Sep 5, 2019 · 2 comments
Closed
Assignees
Labels
config VS Code configuration, set up issues *duplicate Issue identified as a duplicate of another issue(s)

Comments

@slavdok
Copy link

slavdok commented Sep 5, 2019

Much like apache/nginx and linux profile scripts, it would be great if the main User settings.json file had an "include" directive, to load the "next" settings file. All the same settings will be allowed in this "next" file. If there are duplicates, the last one takes overrides the previous.

The rationale is that I can have a "base" configuration, which would be my personal preferences regardless of what environment I am working on, and ability to load/include "work" and "home" specific additions.

As of right now, my "home" and "work" preferences conflict with each other on some specific things, so I keep different settings files for both. But if I want to change some global preferences, I need to remember to do that in both places. This becomes worse when VSCode does an update, and there is a bunch of new preferences to set.

Alternatively, if the main settings.json could support a "per machine" (or an array of machines) settings in addition to global settings, that would also satisfy.

p.s. I know there is per workspace/folder settings, but that doesn't suffice

@roblourens roblourens assigned sandy081 and unassigned roblourens Sep 9, 2019
@sandy081 sandy081 added the config VS Code configuration, set up issues label Sep 12, 2019
@sandy081
Copy link
Member

/duplicate

#17634

@vscodebot vscodebot bot added the *duplicate Issue identified as a duplicate of another issue(s) label Sep 12, 2019
@vscodebot
Copy link

vscodebot bot commented Sep 12, 2019

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!

@vscodebot vscodebot bot closed this as completed Sep 12, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Oct 27, 2019
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