[themes] Put theme configuration to settings.json

[Tyriar]

Having a theme/currentTheme key that could be set in settings.json would be useful in automatically setting the theme in an automated setup. I'm assuming right now it's handled in local storage or something instead?

[aeschli]

Yes, part of your workbench settings that know about recently opened VSCode input, window sizes, cursor positions.
We could put that in the settings. Would we remove it from the File>Preferences menu then? We would loose the theme previewing. If we keep it we would have to ask the user of where to define the theme in user or workbench settings.

[Tyriar]

Couldn't the theme preview just live update the settings.json?

[aeschli]

Which one? User or workspace settings?

[Tyriar]

@aeschli well it would be weird to have a workspace-associated theme, so user. Good point though that there would be a bit of weirdness there. In the end I think it would be good to be able to script your entire vscode setup, themes are the main missing piece in that now that extensions can be installed via the CLI.

[gerane]

I say you keep the two synced. I'd like to have that ability.

[isvoboda]

@Tyriar actually there are situations when theme per workspace makes sense -- I am dealing with the reduced color pallet in the default light+ and dark+ themes which forced me to switch the theme every time I am working with different types of code i.e. workspace.