DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org C4CAD3858402
User-Agent: Cyrus-JMAP/3.5.0-alpha0-4778-g14fba9972e-fm-20220217.001-g14fba997
Mime-Version: 1.0
Message-Id: <1c45d2e7-dde1-45ab-ad24-469b39760d5d@www.fastmail.com>
In-Reply-To: <20220224213229.berg5rjisexeuue3@lucy.dinwoodie.org>
References: <ca3a3890-e097-4a0e-9de1-b91a05c64fa2@www.fastmail.com>
 <20220224213229.berg5rjisexeuue3@lucy.dinwoodie.org>
Date: Thu, 24 Feb 2022 20:45:13 -0500
From: "Anthony Heading" <ajrh@ajrh.net>
To: cygwin@cygwin.com
Subject: Re: pcre regexps in git?
Precedence: list
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>

On Thu, Feb 24, 2022, at 4:32 PM, Adam Dinwoodie wrote:
> I'll see what I can do to get it working again for you!

Adam, that is so nice of you,  thank you!

On Thu, Feb 24, 2022, at 6:54 PM, Allen Hewes wrote:
> Am I missing something?

yup,  "git grep" not "grep"

On Thu, Feb 24, 2022, at 7:27 PM, Yasuhiro Kimura wrote:
> On my 64bit Windows 10 PC `git grep -P` works fine with both cygwin64 and cygwin32.

... which gave me that sinking embarrassing feeling that maybe I had made my own samizdat build of git in a rush one day and left it lying on my path...   :-O   but I think git checks for plain strings before calling the regex engine

/src/zsh% git grep -P _cygpath
Etc/ChangeLog-4.1:      Completion/Cygwin/Command/_cygpath,
Etc/ChangeLog-4.1:      Completion/Cygwin/Command/_cygpath,
Etc/ChangeLog-4.3:      Completion/Cygwin/Command/_cygpath,
/src/zsh% git grep -P _cygp.th
fatal: cannot use Perl-compatible regexes when not compiled with USE_LIBPCRE

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple