onedark.nvim VS gitsigns.nvim

ful1e5/onedark.nvim is completely written in Lua which means it loads way faster. It also supports Treesitter which provides way better syntax highlighting, which dick/onedark.vim doesn't. Lastly, my favourite feature is that it allows you to override/create highlight group configs and pass to the plugin before loading the colorscheme which makes customizing highlight groups super easy (and I would guess faster as well?) compared to calling highlight a bunch of times in your config. Here's What my configuration of it looks like if you're curious.

I use ful1e5/onedark.nvim which is written in Lua and has support for a tonne of Neovim plugins including Treesitter

My favorite is Onedark. There are many implementations but ful1e5/onedark.nvim looks the best imo and is easy to customize and has support for many plugins including treesitter. It's written in Lua.

I'm using https://github.com/ful1e5/onedark.nvim couple of months now and I quite like it. Very pleasing to the eyes. I'm also very found of the utilities in it that are analogous to the tokyonight colorscheme. Best thing to come out of atom imo.

Onedark. I've tried various versions and I like ful1e5/onedark.nvim the best.

Link: https://github.com/ful1e5/onedark.nvim

Can you able to elaborate and attach some screenshots here? I'm really excited to dive in. If I fix this issue, I will create a PR on your repo.

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