From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.home.utahime.org (gate.home.utahime.org [111.108.18.121]) by sourceware.org (Postfix) with ESMTPS id 8E4663857C74 for ; Fri, 25 Feb 2022 00:27:53 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 8E4663857C74 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=utahime.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=utahime.org Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384) (No client certificate requested) by gate.home.utahime.org (Postfix) with ESMTPS id 3CDD54DC11 for ; Fri, 25 Feb 2022 09:27:50 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=utahime.org; s=maybe2019112701; t=1645748870; bh=A6ew3+F28RHePCx3cumVSohznwGMQZRiwJdfE80hUe8=; h=Date:To:Subject:From:In-Reply-To:References; b=XMmS6sGdnVbSnYpLFGTGTfQwu7Ell5mpD1T37z24HIPIIuyaIzxsi6lZBomNkRFXI aD5YAguAvMY/H4xL1wvc89c8r4h7bG0vYm7aLXbCqKdDEUTu5KTAJuhbQhh5y05azi 9KB6pa5b6T7r5SzXecUyGbed3AYBiQprhbQMFyPzU37jfZwH+xvfYWk5HllhIDI97l SykwC4FguYOqsLGmhw2mnqJnmACALtcGCt7+rs7EU4iYKaWy4IrsU+xomtnO9GNOu8 PqS2FBzfrsw1WojUt/M6IMbLEfmZaKawWpTebFaxshxofHfNWLc49vumAod2jXqFaO BSYWidibBSL6Q== Received: from localhost (rolling.home.utahime.org [192.168.174.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384)) (No client certificate requested) by eastasia.home.utahime.org (Postfix) with ESMTPSA id D8EF11416A; Fri, 25 Feb 2022 09:27:48 +0900 (JST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.104.2 at eastasia.home.utahime.org Date: Fri, 25 Feb 2022 09:27:22 +0900 (JST) Message-Id: <20220225.092722.1445422023360153411.yasu@utahime.org> To: cygwin@cygwin.com Subject: Re: pcre regexps in git? From: Yasuhiro Kimura In-Reply-To: References: X-Mailer: Mew version 6.8 on Emacs 29.0.50 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.3 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Feb 2022 00:27:55 -0000 From: "Anthony Heading" Subject: pcre regexps in git? Date: Thu, 24 Feb 2022 16:19:13 -0500 > 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. On my 64bit Windows 10 PC `git grep -P` works fine with both cygwin64 and cygwin32. (Cygwin64)yasu@rolling[1011]% git --version ~/Work/zsh git version 2.35.1 (Cygwin64)yasu@rolling[1012]% git grep -P _cygpath ~/Work/zsh Etc/ChangeLog-4.1: Completion/Cygwin/Command/_cygpath, Etc/ChangeLog-4.1: Completion/Cygwin/Command/_cygpath, Etc/ChangeLog-4.3: Completion/Cygwin/Command/_cygpath, (Cygwin64)yasu@rolling[1013]% --- Yasuhiro Kimura