nvim-oxi VS gitsigns.nvim

How about reading this doc? https://github.com/noib3/nvim-oxi/tree/main/examples

thank you for the support! I'm pretty new to rust (and lua for that matter) so it took me a little while to get my head around how to use mlua in the context of a neovim plugin. Two resources that were really helpful for me were these two github projects: https://github.com/noib3/nvim-oxi and https://github.com/willothy/nvim-utils

nvim-oxi, which uses bindings to the C functions used by the lua API. Note that it's currently broken for nvim nightly, but I'm working on a fix.

I intended to do a rust version but I think it's too easy with nvim-oxi, feel free to take the initiative and make a blazing fast nvim config!

For your problem, there is a new nvim plugin framework nvim-oxi which seems promising, you may have a try.

Lol I started trying to see what that’d look like earlier this year: https://github.com/turboladen/init.rs. It works fine and loads pretty fast. Started by making https://github.com/turboladen/overkill_nvim, but stopped work after https://github.com/noib3/nvim-oxi showed up.

nvim-oxi lets you do it in Rust…

> now that https://github.com/noib3/nvim-oxi has come out, I am going to use it even less.

Woah, interesting ... provided there's success and uptake with this ... I'm imagining it could lead to a really slick and responsive editing experience that those of using (at least) slightly sluggish plugins might have been missing for a while now.

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