Direnv does not unload when changing to a directory without a .envrc

[LeGarbage]

When using direnv in a shell, it automatically unloads the environment upon leaving the directory. However, this plugin does not register when a directory containing a .envrc is exited, so the environment never gets unloaded. If the new directory does contain a .envrc, the new environment is loaded and the old one unloaded at the same time.

Steps to reproduce

Create 3 directories, 2 with a .envrc and 1 without

.envrc 1:

export FOO=foo

.envrc 2:

export BAR=bar

When in directory 1, running :Direnv allow and :echo $FOO gives foo.

After running :cd to directory 2 and :Direnv allow, :echo $FOO is empty and :echo $BAR gives bar.

After running :cd to directory 3, :Direnv allow warns that there is no .envrc in the current directory. :Direnv reload does nothing, and :echo $BAR still gives bar, despite having exited the directory where it was declared.

[NotAShelf]

Thanks for letting me know. I'll probably make this an opt-in feature to reload when changing dirs.

[SkettiSouls]

Sorry if I'm misunderstanding the issue, but is this not solved with a simple autocmd?
I have the following in my config:

vim.api.nvim_create_autocmd('User', {
  pattern = "DirenvLoaded",
  callback = function()
    vim.api.nvim_create_autocmd('DirChanged', {
      once = true,
      callback = function() direnv.check_direnv() end
    })
  end
})

When I :cd to a directory without a .envrc, direnv unloads.
When I :cd to a directory with a .envrc, it loads the new one.

[LeGarbage]

I tried this but I'm still having the same issue. It looks like check_direnv function short-circuits when it does not find a .envrc, so no direnv commands are executed when there is no .envrc, despite direnv itself having this behavior.

[NotAShelf]

Please see if #22 helps

[LeGarbage]

@NotAShelf this helps, but it causes issues when direnv does things like modify $PATH. In that case, when the environment is unloaded, the $PATH variable is unset entirely instead of being reverted. Not sure if I'm underestimating the issue, but direnv itself has that capability, so wouldn't it be simpler and less error-prone to leverage that instead of manually keeping track of each changed variable and unsetting them?