I don't think I said it was. I was addressing the specific use cases mentioned. If there's another use case you think is important in searching command line history, feel free to describe it.

> feel free to describe it

Didn't they already? eg stemming

Most stemming use cases are trivially solved with a regex. That's the point he was making. The difference between a beginner and expert with regexes is quite a lot.

Ahhh, interesting point.

"We could learn advanced regexes... or we could just use FTS5".

Hard call. :)

Well, I suppose what's trivial for me might be advanced for you :)

For regexes, definitely. ;)

Maybe! Full-text search is great for text. Command lines have some things in common with text, but they definitely aren't normal text. E.g., punctuation is much more significant. Stemming may not be appropriate. Case matters. Word boundaries are different, and many of the significant lumps aren't really words.