GNU bug report logs - #32051
26.1; grep-regexp-alist on windows

Previous Next

Full log

Message #14 received at 32051 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Noam Postavsky <npostavs <at> gmail.com>
Cc: 32051 <at> debbugs.gnu.org, Dan.Harms <at> xrtrading.com
Subject: Re: bug#32051: 26.1; grep-regexp-alist on windows
Date: Fri, 06 Jul 2018 11:51:56 +0300

> From: Noam Postavsky <npostavs <at> gmail.com>
> Date: Wed, 4 Jul 2018 15:57:53 -0400
> Cc: Dan Harms <Dan.Harms <at> xrtrading.com>, 32051 <at> debbugs.gnu.org
> 
> Looking at the grep-regexp-alist, it is the case that a filename with
> a colon will not be matched when grep doesn't support --null. In the
> case where grep does support --null, the NUL byte is displayed like a
> colon, so the difference might not leap out at you.

Right, thanks.

> I think the patch below would fix it:

Looks reasonable.  Can we have a test for this use case, so that we
never again regress like that?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.