public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Allen Hewes <allen@decisiv.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: pcre regexps in git?
Date: Thu, 24 Feb 2022 23:54:38 +0000	[thread overview]
Message-ID: <MN2PR17MB3999F2E6F63C92F1A7D58924B83D9@MN2PR17MB3999.namprd17.prod.outlook.com> (raw)
In-Reply-To: <20220224213229.berg5rjisexeuue3@lucy.dinwoodie.org>

> -----Original Message-----
> From: Cygwin <cygwin-bounces+allen=decisiv.net@cygwin.com> On Behalf
> Of Adam Dinwoodie
> Sent: Thursday, February 24, 2022 4:32 PM
> To: cygwin@cygwin.com
> Subject: Re: pcre regexps in git?
>
> On Thu, Feb 24, 2022 at 04:19:13PM -0500, Anthony Heading wrote:
> > Hi,
> > I appreciate this is just a birthday wish-list item, but...
> >
> > % git grep -P hopeful...
> > fatal: cannot use Perl-compatible regexes when not compiled with
> > USE_LIBPCRE
> >
> > It would be lovely (well, at least for me) if this could work.
>
> Huh.  I think that used to work, so if it broke, it presumably broke
> somewhere during the Cygwin Git build process wrangling I've been doing of
> late.  I'll see what I can do to get it working again for you!
>

I use Windows git, but my Cygwin grep doesn't complain:

$ uname -a
CYGWIN_NT-10.0-19044 FOUREYES 3.3.4-341.x86_64 2022-01-31 19:35 UTC x86_64 Cygwin

$ command -v grep
alias grep='grep --color'

$ grep -P allen temp.txt | wc -l
32

$ grep --version
grep (GNU grep) 3.7
Packaged by Cygwin (3.7-2)
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Mike Haertel and others; see
<https://git.sv.gnu.org/cgit/grep.git/tree/AUTHORS>.

$ cygcheck -c grep
Cygwin Package Information
Package              Version        Status
grep                 3.7-2          OK

Am I missing something?

/allen

________________________________

Disclaimer Confidentiality Notice: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender.

  reply	other threads:[~2022-02-24 23:54 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 [this message]
2022-02-25  1:45   ` Anthony Heading
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=MN2PR17MB3999F2E6F63C92F1A7D58924B83D9@MN2PR17MB3999.namprd17.prod.outlook.com \
    --to=allen@decisiv.com \
    --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).