Update direnv example to run in pre_prompt rather than env_change

[johnae]

Any updates to the env should be applied automatically without having to step out/in to the directory again.

[fdncred]

This change will make direnv run before every prompt in every directory, even if you stay in the same directory and just hit enter over and over again. Is that the intent? It seems like there should at least be a check to see if any of the direnv files exist or if the envs are set, but maybe direnv already does that?

[johnae]

@fdncred Yeah that's the intent. @zimbatm could perhaps comment on the efficiency of doing this but AFAIK it is how it's done in other shells.

[fdncred]

@johnae ok, i don't have a problem landing your change but can you please explain why the PWD hook is not working? We may have a bug there.

[johnae]

@fdncred - it's working. It's just that if you change the environment but never leave the directory, direnv won't run and you won't see your changes. I think, therefore, it's more appropriate to run pre_prompt as that results in the expected behavior. I think I was mistaken basically in using env_change when I originally submitted these examples.

[johnae]

What I mean is, if you do change the source of the direnv environment, you want those changes to be reflected without having to step out/in to the directory again (eg. PWD changes). Running pre_prompt solves this.

[fdncred]

understood. thanks for the explanation.