Allow to configure environment variables for extension host

[bl-ue]

I've got a really simple problem: often I open VS Code from a terminal, because I need to run export PATH=... in order to be able to use some extension inside of VS Code that uses a binary to work, e.g., this Lilypond extension, which works really well (thank you @lhl2617!), uses the lilypond external binary.

Perhaps a workspace could have environment variables in addition to project folders? 🤔

[lhl2617]

FYI: you don't need to shove the PATH there :) you can specify the path in the settings.

https://github.com/lhl2617/VSLilyPond/blob/HEAD/docs/INSTALL.md#lilypond-setup-guide

[bl-ue]

Aha! Very nice trick. Dumb of me not to read such a simple guide 😆

Still, the theme of my idea remains the same.

[wickerwaka]

Yes, I agree that the idea is useful even if you specific example can be solved in another way. There are plenty of other cases where being able to set specific environment variables for a workspace would be useful.

[sanmai-NL]

This is important to set universally relevant configurations in a DRY way, such as JAVA_HOME, which is depended on by multiple popular VS Code extensions.