project.nvim VS vim-rooter

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.

This or users may have monorepo style projects and vim-rooter to auto-set cwd to specific directories within the project based on certain file markers (e.g. makefile, package.json, ...etc), to accomplish something like :e dir1/file.go | make would run make and then :e dir2/file2.ts | make would run npm.

maybe you are already doing this and you want to access files outside the project directory but if not I use vim-rooter to set the root dir of the project automatically when I open vim

The airblade/vim-rooter plugin is an essential part of my Neovim workflow. It automatically changes current directory (:h current-directory) for every buffer to a more natural one (like to path of its Git repository). For me this has the following benefits:

It depends where you open vim. If you are in home and open a file (even in sub directories) like nvim directory/file.txt, uour vim's current working directory (aka cwd) will be home. A way to make this automatic I think is the built in autocd (or something like that) and plugins like vim-rooter.

An alternative would be using a plugin like vim-rooter : https://github.com/airblade/vim-rooter

I just use rooter and avoid thinking about it...

There's vim-rooter, which is great.

No, it doesn't change current directory. For that, use sessions or airblade/vim-rooter (or wait around couple of months for planned 'mini.root' :) ). And, of course, you can create custom items which will change current directory.