project.nvim VS lsp-zero.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.

But all that time, my neovim lua config was a copy of other people's configurations, and in the process I had made a mess, and re-sourcing everything didn't work well. It also dependend on lsp-zero, which is a wrapper around other plugins, that I later learned and understood more.

I'm using lsp-zero and i followed this tutorial https://github.com/VonHeikemen/lsp-zero.nvim/blob/v2.x/doc/md/guides/setup-with-nvim-jdtls.md and i have essentially just copy pasted the code from there into ~/.config/nvim/lua/plugin/jdtls.lua

Personally, i think nvim-lint is the best alternative currently, specially so because it has no dependencies on external binaries. This guide assumes you already have your LSP set up with nvim-lspconfig (or an alternative like lsp-zero). You should also have an way to install the linters you are gonna need, i highly recommend Mason with mason-lspconfig.

For those new to neovim, the documentation in lsp-zero has a tutorial that shows a configuration from scratch. It shows how to get a plugin a manager, a colorscheme, and setup lsp-zero.

Try https://github.com/VonHeikemen/lsp-zero.nvim, a great introduction and it is pretty usable without any further config

For neovim, you can still use the same extensions; however there's also a built-in LSP client. The downside of using the built-in is you'll need to have more extensions installed/configured to get all the features out of the box...BUT projects do exist to help simplify that, like lsp-zero.

lap-zero.nvim - default config for nvim-lspconfig, mason.nvim, nvim-cmp.