You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I reported this bug in 2017, but I think I did it wrong at the time since I’m fairly certain I never heard anything back … apologies if it’s actually a duplicate.
The Problem
If a regex with :ignorecase on contains a character which decomposes in case folding into two (or presumably more) characters, only the first character of the decomposition will be matched. Indeed it seems to erroneously push back the end position of the match by one character for the remainder of the match.
I reported this bug in 2017, but I think I did it wrong at the time since I’m fairly certain I never heard anything back … apologies if it’s actually a duplicate.
The Problem
If a regex with
:ignorecase
on contains a character which decomposes in case folding into two (or presumably more) characters, only the first character of the decomposition will be matched. Indeed it seems to erroneously push back the end position of the match by one character for the remainder of the match.Expected Behavior
Actual Behavior
(The last three have ASCII f and i in the string to match, but Unicode fi ligature in the regex.)
Environment
Mac OS 11.2
The text was updated successfully, but these errors were encountered: