Subject: bug#32051: 26.1; grep-regexp-alist on windows

From: Eli Zaretskii <[email-masked]>
Date: Fri, 06 Jul 2018 11:51:56 +0300

> From: Noam Postavsky <[email-masked]>
> Date: Wed, 4 Jul 2018 15:57:53 -0400
> Cc: Dan Harms <[email-masked]>, [email-masked]
> 
> 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?