Open ddickstein opened 1 year ago
Due to Neovim 0.9.0 refactoring the TUI into a separate process, tracking the current working directory in tmux broke. The workaround assumes that DirChanged will fire on all directory changes. This currently does not work with the popd mechanism because DirChanged does not run when triggered by this autocmd (a ++nested is needed): https://github.com/junegunn/fzf/blob/f50a7058d6734b8213fb8bbe6a293b2ffd485eed/plugin/fzf.vim#L618-L621
DirChanged
++nested
Can you provide minimal steps to reproduce the problem you're facing?
And so, simply adding ++nested will fix the problem? Would you mind opening a pull request if this is the case?
Due to Neovim 0.9.0 refactoring the TUI into a separate process, tracking the current working directory in tmux broke. The workaround assumes that
DirChanged
will fire on all directory changes. This currently does not work with the popd mechanism becauseDirChanged
does not run when triggered by this autocmd (a++nested
is needed): https://github.com/junegunn/fzf/blob/f50a7058d6734b8213fb8bbe6a293b2ffd485eed/plugin/fzf.vim#L618-L621