NRK

Pulled the latest master. I get the same on `vim`. I think it's due to this commit https://github.com/mcchrish/nnn.vim/commit/cf3e27c138a7cde9c674795cc3bb822395fc5e56

This should fix it, ```diff diff --git a/autoload/nnn.vim b/autoload/nnn.vim index 6164672..b3835de 100644 --- a/autoload/nnn.vim +++ b/autoload/nnn.vim @@ -386,7 +386,7 @@ function! nnn#explorer(...) abort let l:On_exit = s:explorer_create_on_exit_callback(l:opts) " create the...

> Another problem: > > * open any file in vim > > * open explorer > > * try to exit with `:wqa` > > > I see: >...

> can you step back a few steps in nnn.vim and check where this got introduced? I don't think this is a regression. The same issue happens if you try...

> OK. Any workarounds available? `:w` and then `:qa` should work.

Added a troubleshooting section with the `AutoComplPop` fix. #132

@jarun Checked out `minibufexpl`, I think the behavior of opening on a new buffer is expected. We don't want to wipe the current buffer in case there's unsaved changes. `nnn.nvim`...

> @jarun Checked out `minibufexpl`, I think the behavior of opening on a new buffer is expected. We don't want to wipe the current buffer in case there's unsaved changes....

Aright, so the bug only happens if you invoke `:NnnExplorer` while `minibufexpl` isn't opened. @jarun you can add the following to your vimrc as a workaround: ```vim let g:miniBufExplBuffersNeeded =...

Hmm, the `minibufexpl` problem doesn't occur on `nnn.nvim`, I might look into why that is. However the file rename due to `AutoComplPop` happens there as well, @luukvbaal you may want...