- Jul
- 576
- 10
so i stated using set/r and spent about an hour moving all my env var defs from .btm to .env (my own extension for env var files i read with the set /r command)
Oh wow. Vars that are defined as other aren’t fleshed out automatically.
What i mean is if i put:
whatever_test1=whatever_test1
whatever_test2=%whatever_test1%
Then the correct values will come out with an echo command
But if i read them in perl (and probably in python), whatever_test2 is %whatever_test_1%.
That is, it’s the variable it’s aliased to, and the value is not fleshed out, nor can it be.
Besides researching the aliased environment variable name and using the correct one, how can I avoid this?
Is there a variant of set /r that evaluates aliases, or does this defeat the timesaving? (And if so, maybe that’s what we want to do)
I could always update every perl script but ummmm... ugh. That’s a job for Codex.
Oh wow. Vars that are defined as other aren’t fleshed out automatically.
What i mean is if i put:
whatever_test1=whatever_test1
whatever_test2=%whatever_test1%
Then the correct values will come out with an echo command
But if i read them in perl (and probably in python), whatever_test2 is %whatever_test_1%.
That is, it’s the variable it’s aliased to, and the value is not fleshed out, nor can it be.
Besides researching the aliased environment variable name and using the correct one, how can I avoid this?
Is there a variant of set /r that evaluates aliases, or does this defeat the timesaving? (And if so, maybe that’s what we want to do)
I could always update every perl script but ummmm... ugh. That’s a job for Codex.