cmp-buffer VS gitsigns.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

those are gitsigns. read :h gitsigns-highlight-groups. i think the first 3 ones (gitsignsadd, gitsignschange, gitsignsdelete) would need their background cleared.

I have installed Gitsigns in a Windows machine and when I execute the method diffthis it thinks that the new lines are differences.

Lack of tooling/LSP support compared to Lua. A rather popular neovim plugin, gitsigns, recently switched from teal to regular lua for (among other reasons) the tooling.

https://github.com/lewis6991/gitsigns.nvim/commit/4d63d996b0...

gitsigns.nvim

The closest one would be gitsigns

you can use gitsigns

https://github.com/lewis6991/satellite.nvim absolutely amazing choices, visual economy, integration with gitsigns and builtin vim features (marks).

It's also nice to ask him directly.

For a long time, I have been searching for solutions for asynchrony in Neovim, but what interested me the most was the one provided by gitsigns.nvim. Therefore, I decided to turn it into a separate module to make it easier to use async in Neovim. I have already created some usage examples.

Oh, the symbols are provided by gitsigns.nvim and I have set :h statuscolumn so that they appear to the right of the line numbers. The settings are done in plugin/statuscolumn.lua. I put custom single-file scripts under plugin and ftplugin, where they serve as light-weighted mini plugins, you can even find the prototype of deadcolumn.nvim there :)