public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Anthony Heading" <ajrh@ajrh.net>
To: cygwin@cygwin.com
Subject: Re: pcre regexps in git?
Date: Thu, 24 Feb 2022 20:45:13 -0500	[thread overview]
Message-ID: <1c45d2e7-dde1-45ab-ad24-469b39760d5d@www.fastmail.com> (raw)
In-Reply-To: <20220224213229.berg5rjisexeuue3@lucy.dinwoodie.org>

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

  parent reply	other threads:[~2022-02-25  1:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24 21:19 Anthony Heading
2022-02-24 21:32 ` Adam Dinwoodie
2022-02-24 23:54   ` Allen Hewes
2022-02-25  1:45   ` Anthony Heading [this message]
2022-02-25  1:54     ` Allen Hewes
2022-02-25  8:56   ` Adam Dinwoodie
2022-02-25  0:27 ` Yasuhiro Kimura

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1c45d2e7-dde1-45ab-ad24-469b39760d5d@www.fastmail.com \
    --to=ajrh@ajrh.net \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).