Where to define environment variables in CMD or Clink? about clink HOT 2 CLOSED

Other shells, like Powershell or Bash, have profiles loaded on every startup that could set environment variables.

Clink isn't a shell. Clink adds a few enhancements to CMD, but the question here is more of a question about CMD itself.

so the official way to define environment variables would be inside one of those lua scripts, for example os.setenv("EDITOR", "vim") ?

There is no "official" way to define environment variables in CMD or Windows or Clink. What you noted is one way, out of many different ways.

Since you compared to .bashrc: The way to have a script run every time CMD is launched is to use the AutoRun regkey. But that can be dangerous, as noted in this comment where a subtle bug in an AutoRun script caused an infinite loop of launching thousands of new cmd.exe processes per second.

Clink adds another way to run a kind of "startup" script, but it's only run in a cmd.exe that injects Clink and shows a prompt at least once. See Startup Cmd Script for more information.

from clink.

(This question was originally posted in a very old issue, so I've moved it to a new issue. The original issue answers the question, but there's a newer feature that is only indirectly mentioned there.)

from clink.