todo-comments.nvim VS gitsigns.nvim

Might be triggered by https://github.com/folke/todo-comments.nvim/issues/133

Hello everyone, I am a happy user of both fzf-lua and todo-comments.nvim. I will never thank the authors of these two very useful plugins enough. Now, given that there are a lot of people out there using both and that todo-comments only has a Trouble and a Telescope extension for navigating through the comments, I am wondering if someone ever came up with an fzf-lua extension for todo-comments.nvim. I haven't found it by a quick online search, but maybe someone is keeping it very well hidden in their dotfiles.

I am referring this as well as this this plugin.

For reference, I am referring to this plugin.

If the node isn't defined as a unique syntax token inside the grammar then you cannot change it with queries. You would need to have this change in the python TS grammar, or use a plugin that finds the nodes and changes them (like todo-comments.nvim)

It breaks the highlighting in todo-comments.nvim for me though.

Really depends what you're doing and writing. I'm in a customer facing role and need to often tag my lines with where they belong in my task list. So Folke's [Todo-Comments](https://github.com/folke/todo-comments.nvim) is super handy for me too. I use macros to quickly tag the entire line after I'm done writing it.

Others: todo_comments, comment.

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