Replies: 4 comments 4 replies
-
Basically, i'm looking for an option for |
Beta Was this translation helpful? Give feedback.
-
Are you talking about the filesystem source or the buffers source? |
Beta Was this translation helpful? Give feedback.
-
You have |
Beta Was this translation helpful? Give feedback.
-
Hmm I really can't reproduce. Could you add this to your init.lua and live for a while? vim.api.nvim_create_autocmd("DirChanged", {
callback = function(...)
vim.print(string.format([[Dir Changed (%s): %s]], vim.fn.getcwd(), vim.inspect({ ... })))
end,
}) |
Beta Was this translation helpful? Give feedback.
-
Hi!
Thanks for the plugin, it looks very nice and so far proved to be the most convenient of all the alternatives!
One thing that is bothering me though - I would like to see the list of all open buffers, not the buffers for files in the "current directory". The problem is - if I open Neovim in
~/repo/project1
, thenneo-tree
will happily show all open buffers under the directory. If at some point I do:e ../project2/file.txt
, then openingneo-tree
won't even show that file, since it will still be listing the files under~/repo/project1
.If I run with
dir=/
, to include all possible directories in the tree (because I can runnvim
anywhere in the filesystem), then it works fine for a while, but at some point typing:e <TAB>
starts showing the root of the filesystem, which is not what I'd expect it to do. I wrote "for a while" because the behavior is inconsistent and for some time:e <TAB>
correctly shows the "current directory", but then it all of a sudden switches to/
.Can someone give a hint how to fix this? It would be great to have a setup where the tree lists all open buffers, nicely grouped by their parent directories, regardless of the "current project directory" but with
:e
pointing to it?Thanks!
Beta Was this translation helpful? Give feedback.
All reactions