Jonas Chevalier

direnv has no logic to remove those. Something in the macOS system is filtering those environment variables out. I suspect that `echo $DYLD_LIBRARY_PATH` shows output, and `env | grep DYLD_LIBRARY_PATH`...

It might be the bash that is invoked in the sub-shell.

That's unfortunate... It's a bug but I don't have the time to fix it right now. Do you have some time to look into it?

You can remove any reference to `~/.direnvrc`, it's only there for back-compat. The default should be `~/.config/direnv/direnvrc`

Interesting idea. Is your goal to share the `.envrc` between people on the same project? One approach I have seen is to use `git-crypt` to encrypt the secrets in the...

^ those would be good additions to the [wiki](https://github.com/direnv/direnv/wiki)

Interesting, thanks for all the material. CMD support is probably too legacy and require too much effort/hacks to work properly. Apart from msys I also found an independent port of...

Cool, thanks for looking that up. Are you planning on working on this further ? I would be keen on adding first-class windows support but don't have a development environment.

Alright that's cool too. The core logic is inside of `cmd_export.go` which is executed before every shell prompt. Basically it looks for the file and stores a diff inside of...

That's what's used to parse and execute the `.envrc` files. I wanted to keep the bash syntax and not re-invent a language. I bet it's possible to ship bash as...