Andy Lester
Andy Lester
This has already been done.
I don't really. I just posted that article to Twitter because it was an interesting idea. But it's fine for Indefinite Future.
I'm not sure what the code example is supposed to be showing.
I think something in Perl is getting confused in the regex parser, and this is not an ack-specific problem. Here are some tests I've tried. ``` $ perl -E'$x =...
It looks like the problem is that `fi` with `/i` is seen as variable length, as discussed here: https://stackoverflow.com/questions/50356241/variable-length-lookbehind-not-implemented-but-it-isnt-variable-length Thanks to @wolfsage for pointing me to the StackOverflow answer.
So it looks like the fix is that ack needs to add `/aa` on the regexes it makes. This will stop it from matching ligatures like it did in the...
Bill, thanks for pointing out the other Unicode-related tickets. It may be that Can't We Just.... add `/aa` all over is opening a bigger can of worms.
See also #172
PCRE allows `\Q` and `\E` https://www.pcre.org/original/doc/html/pcrepattern.html
Implementation note: If we allow `\Q` and `\E` we will have to update `is_lowercase` as well.