fidget.nvim VS todo-comments.nvim

I’m experiencing the same but only when fidget.nvim is being displayed

Following a very long slump (and some questionable release management practices), I've finally gotten back into maintaining my own plugin, fidget.nvim, starting with a long-overdue rewrite.

j-hui/fidget.nvim, That is the plugin is causing that. :)

I have been happily using cmdheight=0 for a while now, without noice.nvim. My strategy was simply to add some extra components in the statusline (search result, macro recording, connected LSP servers) paired with fidget.nvim for LSP status updates.

it's up to you how you want to hook these things up, maybe with winbar or statusline, or even a virtual text like in fidget.nvim

Not sure if its specific to you, I just found the lua lsp to be slow af. It takes ages to load the workspace. I use fidget nvim to watch for the workspace to load b4 I do anything.

I have been using fidget.nvim for this purpose for quite a while.

I finally found the culprit. j-hui/fidget.nvim not formatting the long output correctly.

I was buffled by this for a long time and I thought it was a problem in my config as well but I found out that it is normal behavior. I saw it explained in an issue in the sumneko Lua repo but I can't find it at the moment. You can use fidget.nvim for a less spammy lsp report.

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.