project.nvim VS dirbuf.nvim

Here is what I have searched: 1. https://github.com/ahmedkhalf/project.nvim/tree/main : plug manage already exist projects, not create 2. https://neovim.io/doc/user/lsp.html : too complicated 3. https://www.youtube.com/watch?v=NL8D8EkphUw&ab_channel=JoseanMartinez : basic tutorial 4. https://www.reddit.com/r/neovim/comments/ysg4wb/lsp_action_on_multiple_files/ : Mentioned use quickfix, but seems too be a workaround. Not a nice solution.

If someone is interested on this, there is an issue for a feature: https://github.com/ahmedkhalf/project.nvim/issues/73

You can use one of the "rooter" plugins like this one to dynamically change your working directory: https://github.com/ahmedkhalf/project.nvim

https://github.com/ahmedkhalf/project.nvim I have never used this but it seems to involve defining "projects", and any time you enter a project, whatever settings you require (such as current working directory) will get set up for you.

Not sure if this is what you are looking for, but projects.nvim automatically changes your pwd in nvim. If you then use telescope's find_files and to search in the pwd, you basically get project-scoped searches. https://github.com/ahmedkhalf/project.nvim

This works very well: https://github.com/ahmedkhalf/project.nvim

Maybe you have ahmedkhalf/project.nvim setup. In this case, use `manual_mode` as indicated in the readme https://github.com/ahmedkhalf/project.nvim. It worked for me

Not sure what you mean by that. Perhaps your looking for a fuzzy finder. I use telescope for most of this. It can be used to find any file in your project and there's extensions for pulling up projects

project.nvim

Sharing a lightweight plugin I wrote yesterday which provides some functions for accessing previously used current working directories. I know that this is similar to some other "workspace" / "project" plugins which already exist, so I've pasted the motivation section from the README. >I work in a large monorepo and change my working directory depending on what part of the codebase I'm looking at to give my LSP (gopls) a chance and to improve the usefulness of fuzzy finding files. I want to change the current working directory back to a previously used one without having to configure a "project" or "workspace" beforehand. This requirement is not satisfied (as far as I can tell) by existing similar plugins: > - project.nvim > - telescope-project.nvim > - workspaces.nvim. > - neovim-session-manager > olddirs.nvim is very lightweight and doesn't provide any niceties (out of the box) like some of the above plugins, it's literally just :oldfiles for directories. > \ I say "out of the box" since some features like the searching or browsing of files inside a previous directory can be implemented by adding actions to the olddirs.nvim Telescope picker.

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.