I did not run the tests initially... The proposed change impacts more places than i thought initially.

It seems there are also more cases of Keyword + Text instead of Keyword + Text.Whitespace. (run grep -r "Keyword, Text" in pygments/lexers)
That raises the question, is this a design choice?

I've been trying to slowly clean up existing lexers and be more attentive to Text vs. Whitespace in new lexers. It's a pervasive problem to be honest, I wasn't aware how much of a problem it actually already is. This is definitely not by design, but mostly because we didn't pay enough attention to it. If you're interested in fixing this in more places this would be most welcome!

I've been trying to slowly clean up existing lexers and be more attentive to Text vs. Whitespace in new lexers. It's a pervasive problem to be honest, I wasn't aware how much of a problem it actually already is. This is definitely not by design, but mostly because we didn't pay enough attention to it. If you're interested in fixing this in more places this would be most welcome!

This sounds like a problem i can handle. Just a question for the process, would you like individual PRs per changed lexers?

Merged, thanks a lot for working on this!

Thanks for picking this up! I think one PR for everything should be fine given it's fairly easy to review. If you're building any scripts to automate it, it would be great if you could submit them as well should we ever need to go through this exercise again.