telescope-file-browser.nvim VS dirbuf.nvim

EDIT: I found what I was looking for https://github.com/nvim-telescope/telescope.nvim and https://github.com/nvim-telescope/telescope-file-browser.nvim

I'm aware of telescope-file-browser.nvim, but it seems to only search through one directory at a time and not the full project at once.

for reference, what I want it to look like is what they have on the github repo for nvim-telescope/telescope-file-browser.nvim.

an alternative is to use telescope-file browser, which simply allows you to interactively go up/down a directory: https://github.com/nvim-telescope/telescope-file-browser.nvim

I use a lot of key bindings for telescope. A regular use of mine is to open telescope file browser with `` without a previewer, and `` (shift) with previewer. So I have `Layer + f` that sends `` on tap and `` on double tap. Same goes for telescope grep string, but a different config: `` does a live grep in relative folder and `` does a global live grep. Very useful when navigating big monorepos. This is how the layer looks:

There's telescope-file-browser.nvim

hop.nvim to easily hop to specific text with minimal keystrokes

For me I think it’s the best at what it does (with mini.files coming in a close second. It would probably be my first, but I prefer the whole buffer approach over the floating popups.) I’ve tried dirbuf.nvim as well, but I didn’t like that I couldn’t copy/move files.

Big fan of https://github.com/elihunter173/dirbuf.nvim

Shout-out to dirbuf.nvim as it is one of my favorite plugins I cannot live without, but I see it rarely mentioned. It allows you to do file management by editing a file, so you can do anything you would do to edit any regular file. There are no new keymaps to learn, you just use any regular motion, :s, :g, or anything you can think of. Great for bulk renaming!

While I do use file managers often (ranger and dolphin are pretty nice overall), within Neovim my file management is fairly reduced. I use dirbuf when I need to browse through files (for refactors or something), and since it's dired-like its a lot more built into the "vim-as-a-language" mindset. Not to say I do a whole lot in it, but it is quicker than having to do shell stuff within Neovim. I think file-tree plugins tend to just miss the concept for me, as I never found them to be anything more than just "look and see" due to disconnect from the aforementioned "vim-as-a-language"

https://github.com/elihunter173/dirbuf.nvim, it's basically netrw done right.

https://github.com/elihunter173/dirbuf.nvim might just be the thing. In terms of navigating it's as minimal as it can be:

I use fish shell with z plugin to quickly jump to directories and nnn file manager mainly to select files for deletion. I also use dirbuf plugin for neovim when working inside this editor.

dirbuf.nvim!

dirbuf mostly. Anything really advanced and I'll just open a new ranger session

dirbuf doesn't get enough attention. It's a robust, simple, yet featureful replacement for the netrw plugin built into Vim/NeoVim. It allows directories to be treated somewhat like files - edit a directory, and you get a directory listing. That listing can be modified - add files, edit files, delete files, and the result ends up on disk. A much simpler and more-Vimy alternative to tree plugins like NeoTree, in my view.