More trigger-types

[L3MON4D3]

Currently we have regTrig and not regTrig (eg. a plain string), but since lua-patterns are quite limited it would be nice to support full regex via either the soon-to-be included jsregexp or just vims builtin regexes (or just both).
One nice interface for this include retiring regTrig (backwards compatibly) and instead introducing an arg triggerType, which can be

• "plain" for just text
• "lua" for a lua-pattern
• "ecma" for ecmascript-regex if jsregexp is available
• "vim" for vim-regex

[leiserfg]

Currently regex:match_str({str} returns a tuple with the position of the full match, and that does not allow passing the matched groups. Adding that API to nvim should be an easy task, because match_str is just wrapping an internal function that returns an object that contains such groups. I was thinking to make the PR myself (I'm a bit scared after around 6 years without touching C/C++), but I'm ok if someone else takes over it. In any case, it's a blocker, at least if we wanna keep the same API for all the triggers.

[L3MON4D3]

Sadly nvim does not expose a way to get the matches of the regex, only the full match. So if we wanna make it, a PR to nvim will be required. I assume if someone wants complex regexes, probably (s)he will want to manipulate the string as well.

@leiserfg couldn't we use matchlist() in this case?

[L3MON4D3]

Currently regex:match_str({str} returns a tuple with the position of the full match, and that does not allow passing the matched groups. Adding that API to nvim should be an easy task, because match_str is just wrapping an internal function that returns an object that contains such groups. I was thinking to make the PR myself (I'm a bit scared after around 6 years without touching C/C++), but I'm ok if someone else takes over it. In any case, it's a blocker, at least if we wanna keep the same API for all the triggers.

Riiight, theres a lua-api to vim-regexes... Yeah it's tempting to use that, true. I'll take a closer look tomorrow, then I'll understand what you are talking about😅

[leiserfg]

We could start with matchlist and then move to a proper lua API once it's in place, with the only inconvenience of being unable to store the compiled regex.

[medwatt]

Sorry for commenting on an old issue, but is there any update on having proper regex support?

[L3MON4D3]

Finally got to this, follow #923 :D