You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 17, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Jan 17, 2021. It is now read-only.
I think env variables are good, but config file would be better, won't have to pass them everytime..
We can have both, env variables having more priority than config. And config having more priority than defaults
My reason for having a different config file is that other apps should not accidently use those variables. I know this is rare, but possible.
Noone will be going in some other application's configs accidently
Activity
ammario commentedon Apr 22, 2019
Related #29
I think it's best to have these as environment variables.
SscSPs commentedon Apr 22, 2019
I think env variables are good, but config file would be better, won't have to pass them everytime..
We can have both, env variables having more priority than config. And config having more priority than defaults
foresthoffman commentedon Apr 22, 2019
Environment variables can be easily placed in a user's
.bashrcor.bash_profile.SscSPs commentedon Apr 22, 2019
My reason for having a different config file is that other apps should not accidently use those variables. I know this is rare, but possible.
Noone will be going in some other application's configs accidently
ammario commentedon Apr 22, 2019
It's not worth worrying about the chance of another application using an environment variable as specific as
VSCODE_SETTINGS_DIRAllow specifying alternative VS Code settings dirs
Allow specifying alternative VS Code settings dirs
Allow specifying alternate VS Code settings dirs
Allow specifying alternate VS Code settings dirs