Improve handling of environment variables in the pipe transformer about glow HOT 5 CLOSED

An alternative approach is to define environment variables via JSON and put those variables into your script, which is then run through the pipe transformer.

Here's an example,

I have never used the environment variable feature in glow. Probably because I hit the same limitations you describe above!

from glow.

The snake-case parsing of arguments makes it impossible to pass uppercase environment variables, right?
E.g. env_TEST would get translated to t_e_s_t.

Interestingly, passing env_test_path='asdf' results in an environment variable test_path="asdf".
So actually there is no need to parse them as snake-case.

from glow.

Ah, OK, I did not think of that solution 😁

from glow.

will keep the issue open for now until this is properly documented

should delete those environment variable options from the docs, they are somewhat confusing

from glow.

updating the example in the docs to avoid this issue in future:

#490

from glow.