-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
regex matching appears to not work. #2
Comments
interesting... I can clearly reproduce the issue in production... working as expected on my sandbox |
Also for the sake of clarity, it would be a good idea to label the search as PCRE regex, as git does not use Perl regex. |
@Grinnz the interesting thing about that is that the git grep command line option is actually: "--perl-regexp" |
Yes, but it is mislabeled. The man page specifies that it is linking to libpcre. |
|
git was not compiled with lib-pcre on the server, need to recompile it with pure among other dependencies, looks ok now in production |
git build process for 2.13.3:
|
For informations, after recompiling a few requires libraries, here is the command I run to recompile git in my user directory with pure support
List of required dependencies:
and then git itself (version 2.13.3) |
The first things I tried included whitespace matches and character classes:
sub\s
returns no matches: https://grep.metacpan.org/search?size=20&q=sub\s&qd=&qft=do\s
returns no matches: https://grep.metacpan.org/search?q=do\s&qd=&qft=[s][u][b]
returns no matches: https://grep.metacpan.org/search?q=[s][u][b]&qd=&qft=[ ]
returns (a character set including only space) no matches: https://grep.metacpan.org/search?q=[+]&qd=&qft=The text was updated successfully, but these errors were encountered: