oil.nvim VS gitsigns.nvim

Oil is great: https://github.com/stevearc/oil.nvim

It just treats your file structure as a buffer

Hey , i'm using oil.nvim, it does integrate LSP rename file, but currently if you code in js you must apply this pull request https://github.com/stevearc/oil.nvim/pull/248 to fix refactor js ,ts file. (warning: the author says this pull request doesn't work with all pattern maybe it will be updated in future )

File explorer: oil.nvim

Hello, i've tried Oil.nvim and liked it , but when people talk about it , in general questions about FileTrees and File Browsers people really swear by Oil.nvim and got me wondering,what am i missing?

A very nice plugin which I use whenever I have to edit/create multiple files is oil.nvim

For those that want this to replace `oil.nvim`, here are the keymaps I added to my config for it to behave the same as oil. The dash keymap will open `mini.files` in the current directory from the file you triggered the keymap. The `fe` keymap opens the `mini.files` at the root directory so you can use it like your file manager. I like that the location you leave the window when opening with `fe` is not affected by the location you leave the dash trigger. I hope that map makes sense. I use NvChad, so my mapping looks like this, but you should be able to use it in any distro or custom config.

https://github.com/stevearc/oil.nvim - file explorer

Maybe https://github.com/stevearc/oil.nvim? Nvim tree and neotree both have floating mode as well which I prefer more.

I use oil.nvim.

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