todo-comments.nvim VS trouble.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.

Does anyone know if it's possible to copy the LSP diagnostics (which currently is being displayed using folke/trouble to the quickfix window?

A newbie here, I used jose-elias-alvarez/null-ls.nivm for diagnostics and formatting, but I recently discovered folke/trouble.nvim and for me, it seems like a better option However, I don't know if it supports formatting and linting, I don't even know if it is an alternative to null-ls. So I need your help, can trouble.nvim replace null-ls? If not, can I use both of them simultaneously?

Trouble

Looking at the screenshot here for example https://github.com/folke/trouble.nvim they show errors both in the gutter and underlined.

All you need is just the LSP working (with linter, formatter and diagnostics) and telescope. Seriously, telescope is the GOAT, way faster than a file tree, you end up using the filetree only to move, create and delete files/folders but if it's just for that, you might as well use the terminal instead. For the LSP, it's not only autocompletion and hints at hover but formatting and diagnostics. I use lsp-zero + null-ls + trouble. I exposed all of the keybindings on those so I can at least open my own configs for guidance. Oh yeah, having treesitter is probably a must too, and it has no keybindings on its base form.

I am referring this as well as this this plugin.

Trouble: https://github.com/folke/trouble.nvim

Trouble is so good for finding errors easily. For testing I use jest so I haven't had too many issues. What do you test with?

I like trouble.nvim

I guess LazyVim uses https://github.com/folke/trouble.nvim for it. I should config it to not including errors regarding standardization.