how to hightlight the string "TODO" in markdown

[ilcpm]

I use the default setting for BTT.

In my use case, I use "TODO" string in markdown document to note down what todo next.
But I can't find an option to hightlight this string. I read the default regex string, looks like it should match the bare string "TODO".
So I don't know what should I do. In the original todo-tree, this is a default feature.

[ilcpm]

"TODO" is hightlighted only when the line is a comment, can anyone tell me how to change this?

[it-smconsulting]

Same issue here, TODOs are not highlighted nor recognized by the tree panel on markdown files.

While inserting the TODO inside a comment<!--TODO--> highlights the TODO, it is not recognized by the tree panel.

On other files such as .py the TODOs are highlighted and listed

I'm using vs code 1.130.0 and better-todo-tree 1.3.4

[TomCab]

I can confirm that Better-todo-tree version 1.3.4 running on VS Code version 1.134.0 on a Debian 13 host highlights only tags inside comments when editing Markdown files, as previous users have described.

In my case, however, the tags are shown twice in the tree panel, when the description of the tag inside the comment is empty. This means the comment <!-- TODO --> is displayed in the tree panel as:

"TODO TODO"

When a description of the tag inside the comment is present, the tree panel works as intended, e.g. comment <!-- TODO: example --> is displayed with its corresponding icon in the tree panel as:

TODO: example

The same behaviour occurs with other tags, like FIXME, or BUG.

In some ways this behaviour makes sense, since (a) this way HTML generated from Markdown files is not cluttered with TODO, FIXME, BUG, and other tags intended only for the developer and (b) using tag descriptions is encouraged by the duplicate tab display in the tree panel.

Please let me know if this behaviour is intended, then I would gladly create a short PR with a description of the expected behaviour under section Markdown Support in README.md.

[FanaticPythoner]

First, I wanted to say, sorry for being AWOL for a while. Lots of things moved in my personal, and professional, life, including expecting, unexpectedly, yet happily welcoming such, a new member in the family. I will get back to Better Todo Tree in the very short term. Thank you for you guys' understanding ❤️

[FanaticPythoner]

Even though I've sent tthis comment in all open issues at this time on BTT, be assured that I will carefully review your spefific case and answer you, in the next few days, to a week, personally and appropriately. Thank you, and you surpport means a LOT!!!!!