workspaces.nvim VS lsp-zero.nvim

`:tcd` into that project's folder. I'm using workspaces.nvim to create aliases for my project's folders, so I can simply do `:WorkspacesOpen MyProject`

workspaces.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.

i use workspaces for that, https://github.com/natecraddock/workspaces.nvim

I use https://github.com/natecraddock/workspaces.nvim and their compatible session manager. I have not tried the other two but workspaces works well and has done nice integrations (including telescope).

I use only one neovim instance and with the plugin https://github.com/natecraddock/workspaces.nvim I change between repositories.

I'm biased, but my favorite is a combination of workspaces.nvim and sessions.nvim (I created both). Both are extremely simple frameworks meant to be customized to your needs. Not for everyone, but if you are looking for something simple its worth giving a look.

workspaces.nvim

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.

In version v2.x the keybindings you set on the "global" on_attach of lsp-zero should work without any extra config. v2.x also has a tutorial on how to work with nvim-jdtls: setup with nvim-jdtls

Creator of lsp-zero suggested a complete solution to use ray-x/lsp_signature in this issue: https://github.com/VonHeikemen/lsp-zero.nvim/issues/69.