cmp-buffer VS mason-lspconfig.nvim

sources = cmp.config.sources({ { name = "nvim_lsp", priority = 1, group_index = 1 }, { name = "luasnip" }, { group_index = 2, name = "buffer", priority = 5, option = { -- https://github.com/hrsh7th/cmp-buffer get_bufnrs = function() return vim.api.nvim_list_bufs() end, }, }, { name = "nvim_lsp_signature_help" }, { name = "path" }, }),

cmp-buffer: Completion source. It provides suggestions based on the current file.

Then what is the purpose of using cmp-buffer?

Okay I sat down and did exactly what I said in my previous comment. Essentially it's a complete rewrite of my old code that makes things much more generic and flexible. You can take a look at the PR here: https://github.com/hrsh7th/cmp-buffer/pull/60.

Good work but can you tell how is it different from https://github.com/hrsh7th/cmp-buffer

hrsh7th/cmp-buffer - nvim-cmp source for buffer words

cmp-buffer

nvim-cmp is just the autocompletion engine w/ fuzzy matching and other filtering options. To get items to be filled from cmp you will need sources, for example: hrsh7th/cmp-nvim-lsp plugin will provide items from a LSP server to cmp, so you can get items you can fuzzy match in. Another one is items from buffers: hrsh7th/cmp-buffer

https://github.com/hrsh7th/nvim-cmp This is an autocompletion engine https://github.com/nvim-treesitter/nvim-treesitter This allows NeoVim to install parsing scripts so NeoVim can do things like code highlighting. https://github.com/williamboman/mason.nvim Not strictly necessary, but allows you to access a repo of LSP, install them, and configure them for without you actively messing about in config files. https://github.com/neovim/nvim-lspconfig Also not strictly necessary, but vastly simplifies LSP setup. https://github.com/williamboman/mason-lspconfig.nvim This lets the above two plugins talk to each other more easily.

pylsp offers an option to install flake8 as an optional plugin and Mason offers a command to install pylsp plugins. I could then install flake8-pytest-style via pip. Then pylsp and flake8 would live in the same Mason environment and flake8-pytest-style would live in my project's environment. I don't know if/how they will communicate with each other.

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.

Have you set up https://github.com/williamboman/mason-lspconfig.nvim as well?

You can also use https://github.com/williamboman/mason-lspconfig.nvim with nvim-lspconfig to make language server installation closer to installing a vscode extension, in that you just install a language server through mason and it'll be automatically configured for you.

https://github.com/williamboman/mason-lspconfig.nvim - Mason plugin to manage your LSP servers.

I found this GitHub issue: https://github.com/williamboman/mason-lspconfig.nvim/issues/224 I think it could be related, but I'm not sure.

LSP: lspconfig & mason-lspconfig.nvim"