FEATURE REQUEST: Support for variable substitution when defining environment variables #9113
-
It would be great if we could define environment variables as a function of other variables. VS Code seems to support this, though I haven't used it enough to know its limitations and intended uses. For example:
or
I would want to be able to set workspace environment variables that reference user and system environment variables. ![]() |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Hey @jeffkeller-einc! Great to see you're using the environment variables feature. I gave this a test myself, and found that system environment variables defined outside of Positron work as you'd hope. For example, However, I do also see that variables defined in Positron don't resolve this way. So, your It sounds like that latter case would be really useful, and I can create an issue from this feature request to get the idea working its way into Positron. What are your thoughts, given the ability to substitute outside variables? |
Beta Was this translation helpful? Give feedback.
Hey @jeffkeller-einc! Great to see you're using the environment variables feature.
I gave this a test myself, and found that system environment variables defined outside of Positron work as you'd hope. For example,
SUPER_IMPORTANT_DIR="${env:HOME}/path/to/dir"
resolves to/Users/me/path/to/dir
.However, I do also see that variables defined in Positron don't resolve this way. So, your
SERVICE_URI
example doesn't work.It sounds like that latter case would be really useful, and I can create an issue from this feature request to get the idea working its way into Positron. What are your thoughts, given the ability to substitute outside variables?