The very useful addon that displays a call tip colour-swatch when hovering over a legit colour hex value, is unfortunately a little overambitious when it parses text for a hash character followed by a string containing letters A-F, it seems.
For textual contexts in which misinterpretations become frequent this can be quiet annoying. Specifically, whenever the cursor "touches" an occurrence of a #define-directive (in a C-file), a lightblue calltip swatch keep popping up, blocking the text! The bug here, of course, is the fact that the string #DEF... is simply interpreted as a hex value.
I don't know how this functionality of the plug-in can be made to robustly distinguish between "correct" hex strings and C-like directives, for example. Perhaps an option to check for file type, so it doesn't even try parsing files with certain filename extensions like .c, .h., .cpp, .ino etc?

If "somebody" contributed a pull request that allows a (preferably user settable) list of filetypes to include/exclude is probably an improvement.
@elextr I see your point. Wish I was somebody :-)
Know my limitations when it comes to app coding, though. So better stick with the embedded stuff.
github-comments@lists.geany.org