languageserver VS nvim-cmp

Symbol outline by LSP Client: It can connect to any LSP "server" (runs locally) which implements LSP protocol (https://microsoft.github.io/language-server-protocol/), and supports "stdin" communication. A number of LSP server configuration is provided by default (including R), but user can extend, and override this configuration. As long as the LSP servers are properly installed (kate will start them) and the Kate LSP client configuration is set up properly should work. LSP also provides other IDE-like features (like code completion, jump to symbol definition, diagnostic/linter messages) etc. I found an LSP server for R (https://github.com/REditorSupport/languageserver), you may want to give it a shot.

You'd need: - hrsh7th/nvim-cmp with set up LSP source (hrsh7th/cmp-nvim-lsp). - neovim/nvim-lspconfig. - R language server installed. This is a regular R package, can be installed from CRAN.

Besides a common modern Neovim "IDE setup", some other useful R-specific tools: - languageserver R package for LSP integration. - styler R package for code formatting. Somewhat slow and lacks some features, but seems to be the best current solution.

First of all, make sure that you actually use r_language_server. For that, at least install languageserver R package (run R from command line and execute install.packages("languageserver")) and set up r_language_server with nvim-lspconfig. I think after that you should be able to see some diagnostic information.

The truth is that most editors will use R language server underneath ( https://github.com/REditorSupport/languageserver ) so it's more what layout you prefer than what functionalities an editor has to offer.

Other plugins/utilities can fill in some of the other gaps. In the screenshot below, I'm using NvimTree to browse files, and I'm also currently using Neovim's native LSP client (in Neovim 0.5.0) with r_language_server installed (configured with the Neovim team's plugin nvim-lspconfig).

you can use nvim-lspcofig for LSP support, mason.nvim for installing LSP servers, linters, formatters and debug adapters. nvim-cmp for completions, luasnip for snippets, null-ls for configuring your formatter and linters , lsp-inlayhints for inlay hints.

Hey all, I use nvim-cmp and love it. One item I've wanted to have but can't seem to get is multi-line completion. For example, a for-loop suggestion only gives me the first line of the for-loop, I'd love to get the entirety of the suggestion to be inserted with one selection. I'm sure under-the-hood the copilot has it.

hrsh7th's nvim-cmp is used for auto-completion, as recommended by neovim/nvim-lspconfig.

nope it's https://github.com/hrsh7th/nvim-cmp/ , if you look at the first video at the 5-7 second mark it's possible

Right now the standard plugin for autocompletion is https://github.com/hrsh7th/nvim-cmp

For those who don't know, lsp-zero is a plugin that bundles a configuration for nvim-lspconfig and nvim-cmp. The original idea was to make a setup for the built-in LSP client that didn't require too much effort.

I think cmp-cmdline is what you're referring to? It's an extension of nvim-cmp.

How do you get it? Well, actually if you press CTRL + n you will get a built in completion window. However, the little popup box that follows each letter that you're used to in other IDEs is not standard out of the box with neovim, you need to install a completion plugin. Most people use https://github.com/hrsh7th/nvim-cmp.

Also I suggest adding the lsp completion source as shown in the readme. Lastly, the wiki has a guide on changing the appearance of you are trying to get it closer to vscode https://github.com/hrsh7th/nvim-cmp/wiki/Menu-Appearance

I wonder if it is due to my cmp configuration? Source of my cmp is configured as followed: lua sources = cmp.config.sources({ { name = "nvim_lsp", entry_filter = function(entry, _) -- Kind enum: https://github.com/hrsh7th/nvim-cmp/blob/main/lua/cmp/types/lsp.lua#L178-L204 -- if kind is Text, then filter if entry:get_kind() == 1 then return false end return true end, }, { name = "luasnip" }, { name = "buffer", keyword_length = 4 }, { name = "path" }, }),