This leaves patch list text unaltered so that it doesn't differ from the commit history.
https://github.com/vim/vim/pull/21153
(6 files)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()
okay, it seems regexp is more commonly used through the documentation than regex. Fine, although personally I prefer regex over regexp, but 🤷
Makes me wonder, do we need to blacklist certain terms for the documentation? Something that we can add to the test_codestyle?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()
In the help content it was about 10 to 1 and all the related tags and options (e.g., 'regexpengine') use it.
I can add something to test_codestyle if you like but we'd also have to maintain exception lists as we do for whitespace because some uses of "regex" are external references.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you are subscribed to this thread.![]()