envFile config option

[roamiiing]

Many popular debuggers (node, python, etc.) for VSCode support the envFile option. Also, it's mentioned in VSCode's docs.

Personally, I'd use this option to be able to debug my rust project which needs some API keys. I might use some rust libraries that load env variables from a file, but I think that the program itself should not be responsible for this.

Also, I'd be happy to implement it myself and open a PR. As far as I understand, this might be implemented by adding a dotenv dependency to package.json and using it to parse the file from the new envFile option. Then the env variables might be spread in the env dict:
https://github.com/vadimcn/vscode-lldb/blob/master/extension/main.ts#L178

Let me know if adding a new dependency to this project is appropriate. Also, are there any other places that depend on the env option?

Thanks!

[vadimcn]

Yeah a PR would be nice. Please see the previous issue on this: #506.

[vadimcn]

Implemented in v1.9.1

[default-writer]

Implemented in v1.9.1
So cool! Thanks! i have to use getenv(..) in C bootstra GUI mode, because .env did not worked at all, maybe thing will change soon!