Utkarsh Raj

Hi, any update with this, I think it's confusing that the script doesn't even at least mention this issue, nor is it mentioned with the documentation. I believe it's worthwhile...

Python `virtualenv` module does handle each shell in shell-specific manner. It has a similar problem to set environment variables for these different shells. For Unixy systems they have multiple versions...

Maybe this can be expanded to include log4j, which has the similar requirement to set system property, `-Dflogger.backend_factory=com.google.common.flogger.backend.log4j.Log4jBackendFactory#getInstance` This as far as I could find wasn't mentioned in either https://google.github.io/flogger...

looking at logs would be the best bet, since this doesn't tell anything. i have seen such problems often when environment variables aren't configured probably, so that could be the...

After `sudo login` I am able to use variables set in /etc/environment. Interestingly WSL with Ubuntu doesn't seem to read variables set in ~/.pam_environment