Doesn't handle whitespace. Searching for "pro" returns comments that contain standalone instances of "pro" but also any comment containing a string with pro in it, like "pronounce" or "product." That's fine, but then if I search for "pro " with a space after pro, I get the exact same results.

Also, and this is not a big deal, it highlights substrings that are one character shorter than what you type in. So when I searched for "pro" it for some reason highlighted any instances of "pr" in the comment. Note that this doesn't actually affect which comments are returned, it's just a highlighting issue. So if you search for "pro" and a comment said "practice profiling perps," it would show up as a search result, and the pr in practice and the pr in profiling would be highlighted. But if a comment said "practice running," it would not show up as a result, so that's good.

Edit: thank you for the response! If I click "extended search" then searching using whitespace (in quotes) does indeed yield the correct results. As noted in that github thread, it no longer highlights the identified string in the comments when extended search is checked, but that's no big deal. Also the issue I mentioned with it highlighting a string that's one character shorter than the string searched for is not happening today, so that's cool.