Jonas Chevalier

Sounds good! Is the Linux version of PowerShell close enough to be a realistic target for testing?

yes if PowerShell for Linux can be installed under WSL then it's fine for development, most likely it will also be installable in Travis

I wrote a quick version here: https://gist.github.com/ee97a194d77f162550b0347890eff120 It didn't require to extend direnv itself as PowerShell can read JSON. As you can see I decided to hook into the Global:prompt()...

@f0ff886f I don't use PowerShell day-to-day so that was more of a quick experiment, with the hope that somebody would pick this up and submit a PR

@f0ff886f can you give me the output of `direnv status`? It looks like direnv is not able to load the output from the stdlib, which is sourced by running `eval...

This might be a windows path formatting issue again. The direnv exec path has forward slashes but not the others.

The `.envrc` format is always interpreted in bash. the direnv extracts the environment diff and re-exposes it to the target shell. the project is not running on Azure Pipelines so...

Thanks, is there any test that could be run to verify this behaviour?

It looks like direnv triggered a bug in bash. Without a core dump it will be too hard for me to reproduce the issue.

What do you have in `echo $PROMPT_COMMAND`? Are there any other entries than direnv there?