Allow syncing all files and folder located in ~/…/Code/User/. Some important extensions settings are there.

[Fred-Vatin]

For instance, there is the folder named globalStorage where some extensions store their settings (color-manager). @royaction

Project Manager store projects settings in ~\…\Code\User\projects.json. See alefragnani/vscode-project-manager#431.

There may also be …\Code\User\Emmet Settings\snippets.json if you set it so in

"emmet.extensionsPath": "${env:APPDATA}\\Code\\User\\Emmet Settings",

Currently, it can only be handled by shanalikhan sync extension or zokugun Sync Settings not the built-in settings-sync.

Users and extensions devs are waiting for a built-in solution. A glob pattern to pick which files and folder to include would be appreciated.

[gjsjohnmurray]

/assign @sandy081

[sandy081]

Extensions can now synchronize state in globalStorage, please file an issue against them.

[Fred-Vatin]

Extensions can now synchronize state in globalStorage, please file an issue against them.

Nice but what about other files like …\Code\User\Emmet Settings\snippets.json ?

[sandy081]

How different are these from regular user snippets ?

[Fred-Vatin]

How different are these from regular user snippets ?

https://docs.emmet.io/customization/snippets/

I personally use this by duplicating huge default emmet snippets and overriding them with customization when needed and some addition.

[sandy081]

Is it supported by an extension?

[Fred-Vatin]

Is it supported by an extension?

No, it is an emmet feature controlled by this setting

"emmet.extensionsPath": "${env:APPDATA}\\Code\\User\\Emmet Settings",

Allowing custom folder in code\user to be synched would make VSCode user environment truly…synched.

[sandy081]

I see, this is coming from built in emmet extension. At present we do not support custom user files from extensions. I would use this issue to track that feature.

[TylerLeonhardt]

https://github.com/alefragnani/vscode-project-manager would love to see this for their projects.json's

[majkinetor]

Its essential feature, this way sync is half baked.

[vscodenpa]

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding, and happy coding!