nvim-scrollview VS gitsigns.nvim

For scroll bar, try nvim-scrollview

Nice. I was using dstein64/nvim-scrollview for scrollbar, but I am now tempted to switch to this one for search/gitsign integration.

Here are a few ideas to help: - Make sure your cursor stands out and is easy to find - Briefly explain windows, the status bar, and the tab bar, and make sure he knows that the file names are indicated at the BOTTOM of a window in the status bar - Make sure you have line numbers turned on and perhaps use this scrollbar plugin https://github.com/dstein64/nvim-scrollview so he knows where in a file you are - Explain what you are doing constantly, especially if the screen appears to be changing all of a sudden e.g., when you are scrolling up/down, jumping to the next search match, jumping through the jump list, jumping to a code symbol, navigating to a new file, opening up a file explorer, opening a fuzzy finder, opening a terminal, etc.

Virtual text. Diagnostics/linters are the obvious use case here, but there are other clever uses that plugin authors can use this for. (indent-blankline, nvim-scrollview, ...)

I use neoscroll for smooth scrolling and if you want a scrollbar then use this https://github.com/dstein64/nvim-scrollview

As of 79797a0, this workaround and a few others are now applied automatically. Workarounds that would clobber existing customizations are not applied.

I tried various ways to approximate WinScrolled, including usage of CursorMoved, but was unsatisfied with the options I tried. I documented some of the issues here. I recall also encountering an issue in Vim where the popup window for the scrollbar would occasionally become the active window, but I didn't spend much time debugging that, having switched to developing the plugin for Neovim.

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