tig-explorer.vim VS gitsigns.nvim

I use tig-explorer which allows to launch tig from vim (not really impressive) but open file from tig back into the parent vim (the interesting bit).

Tig combined with this vim plugin is big part of my workflow: https://github.com/iberianpig/tig-explorer.vim

In addition to the above I love tig for quick commit viewing: https://github.com/iberianpig/tig-explorer.vim

For a git tree, there is a lot of plugin that can be integrated. I use TIG integration with https://github.com/iberianpig/tig-explorer.vim or switch directly to terminal with git log --graph

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 :)