diff options
| author | Barrett Ruth <62671086+barrettruth@users.noreply.github.com> | 2026-07-13 14:10:19 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-07-13 15:10:19 -0400 |
| commit | 73bb6a8a5e3fa20336e27159df4b9112b33398bc (patch) | |
| tree | 1e396f07b5c3bd3f2a5546e5ccf68bb89da38d8e /test/functional/vimscript | |
| parent | 4d736cd41feb863274ccc73cf9e10407bdddd913 (diff) | |
| download | rneovim-73bb6a8a5e3fa20336e27159df4b9112b33398bc.tar.gz rneovim-73bb6a8a5e3fa20336e27159df4b9112b33398bc.tar.bz2 rneovim-73bb6a8a5e3fa20336e27159df4b9112b33398bc.zip | |
fix(dir): let 3P dir-browser plugin rename the dir buffer #40529
Problem:
`FileType directory` fires *before* the `BufEnter` path where `dir.lua`
populates the buffer, in order to allow a 3P dir-browser plugin to handle the
event and (optionally) rename the buffer to e.g. `example:///tmp/foo/`.
But currently, `open_buffer()` continues after `filetypedetect BufRead` as if
the original directory buffer is *still* current and valid, which may fall
through to the built-in `nvim.dir` path after a 3P plugin ALREADY handled the
directory.
Solution:
Keep a buf ref around the early `filetypedetect BufRead` call for directory
buffers.
If the `FileType directory` handler switches away from/deletes the original
directory buffer, stop the open path instead of continuing into the built-in
`nvim.dir` flow.
Diffstat (limited to 'test/functional/vimscript')
0 files changed, 0 insertions, 0 deletions