[Feature Request] Multi Line Comment Highlight
Hey, awesome plugin, I really like it, but I find myself writing a lot of multi line comments.
Currently, they are highlighted like this:
This really bothers me and It would be cool to extend the highlighting of comments to the next line, if the Indentation of the first character aligns/matches.
I was about to request the same feature, any update? Is it possible?
I came to suggest the same feature, looks like I'm in good company.
I think this would be a nice feature as well.
Any updates on this?
@wizard-28 just wait or implement it yourself. It’s considered bad form to bump a feature-request like that.
This can probably be done using Treesitter right? Might take a stab at a PR for this some time this weekend or next week or something.
Very keen for this! It's the only feedback i'd have for this great plugin. I'm happy to help get a PR in if someone has already had a go, other wise i'll try to have a go in the coming weeks if I find time
Same question, now I disabled non-keyword highlight to make multi-line comments look suitable:

My config:
require("todo-comments").setup {
signs = true,
highlight = {
before = "", -- "fg" or "bg" or empty
keyword = "bg", -- "fg", "bg", "wide" or empty. (wide is the same as bg, but will also highlight surrounding characters)
after = "", -- "fg" or "bg" or empty
comments_only = true, -- uses treesitter to match keywords in comments only
max_line_len = 400, -- ignore lines longer than this
exclude = {}, -- list of file types to exclude highlighting
pattern = [[.*<(KEYWORDS)[^:]*:]],
},
}
I actually have found this to be a good thing because it forces me to write concisely a 'title' and then all following lines are my extra context. Just my two cents.
I just pushed an update that implements this
Cool addition, works great! The only thing I find a bit weird is how each line adds an entry to the sign column, as opposed to just the line containing the relevant KEYWORD.
Works wonderfully, thank you!
although I have to agree with @daephx, the signcolumn entry for each line of the comment looks a bit odd
Right, forgot about that. Fixed!