Issues with profile Settings and user Settings

[ipsfsw]

The Settings of the profile are isolated from the user Settings and the relationship between them should be modified.

The Settings of the profile should be an extension of the user Settings, that is, the Settings of the profile should inherit from the user Settings, just like the workspace Settings for the user Settings, if the user set option is not overridden, the option is the user set.

When we use vscode, the layout of the interface or some global plugin Settings are determined, so it only needs to be kept in the user Settings, rather than changing this option in every profiles Settings.

I submitted this feature request to be considered because I found some inconsistencies between the profiles Settings and the user Settings while using vscode. For this feature, my idea of change is in order of priority: workspace Settings (.vscode/setting) > profiles Settings > User Settings > default Settings. This sort of prioritization.

[anthonyvdotbe]

This is a duplicate of #156144, isn't it?

[ipsfsw]

Yes, excuse me for not seeing the question #156144.

I went to read the discussion and the question is very correct, because in vscode and other editors, we need to enable different development environments for different projects. In these different development environments, we really want many of our configurations to be the same, such as shortcut key Settings, Because I used neovim, saving ctrl + s was removed from the shortcut list, making it easier for :q / :qa. So, in the course of using profiles, the plug-ins and editors that we need to use globally do not need to change their configuration. Of course, there may be special requirements to override certain configurations.

I like vscode very much and thank you for your development.

Thank you very much for your reply.

[sandy081]

/duplicate

[vscodenpa]

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 similar existing issues. See also our issue reporting guidelines.

Happy Coding!