Allow for :DirenvAllow command

[jalcine]

Similar to how :DirenvExport works, being able to do :DirenvAllow after editing a .envrc file would be handy for those of us not eager to spin up a little terminal window each time configuration is changed.

[zimbatm]

👍 maybe @delphinus would be up for implementing this or yourself?

[jalcine]

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512

On Saturday, July 7, 2018 8:36:29 AM PDT zimbatm wrote: 👍 maybe @delphinus would be up for implementing this or yourself?

I'm down to implementing this! - -- - ---- jackyalcine Learn more about me at https://jacky.wtf Reach out with inquiry at https://jacky.wtf/contact/ Ready to work on your tech project? Visit https://jacky.wtf/work/ -----BEGIN PGP SIGNATURE----- iHUEAREKAB0WIQQpf42sRlb1z6vNm29Tek+QSxUmjQUCW0Ds8QAKCRBTek+QSxUm jWSkAQDFvCZhlBJA8c4GEcqRYInNCmiz0A6CKIQqvFJIiB64HQD/cpqma9Di2iQO ZrdOhMAjlZaWpFXdQwXLvZ85FGpcg2g= =gj/l -----END PGP SIGNATURE-----

[zimbatm]

great! looking forward to the PR

[timokau]

Related:

When vim is running and I change the .envrc it sometimes shows a warning (mentioning that I need to allow) and sometimes it doesn't. I have no issue with opening a terminal to allow the changes, but it would be nice if there was a reliable notification.

Then when I do open a terminal and direnv allow, vim still won't reload the environment (probably because DirChanged is not triggered). Maybe direnv could somehow trigger a change on direnv allow. Something like date -Ins > .direnv-update && rm .direnv-update might work, though there could be race conditions.