Re: problem with recent change to grep-regexp-alist

[David Kastrup <dak@gnu.org>]

Juri Linkov <juri@jurta.org> writes:

>> In the 1.42 revision of grep.el the subpattern for the filename in the
>> regexps of the first two grep-regexp-alist's elements has been changed
>> from "\(.+?\)" to "\([^:\n]+\)". Now the matching fails if the
>> filename contains a colon, while the previous value worked, thanks to the
>> non greedy "+?" quantifier. Note that the regexp of the third
>> grep-regexp-alist's element is still correct, and is the one that
>> matches if grep-highlight-matches's value is "t" (which is the
>> default).
>
> Ok, let's use "\(.+?\)".
>
> You can still get wrong matches with the file names like "abc:123",
> but perhaps such file names are rare.

Maybe \([A-Za-z]:\| ...
or something?  It is not like there are many Unix file names starting
with a single letter followed by colon.

But Linux has file names like

/proc/driver/uhci/0000:00:07.2

which might not be terribly relevant, but better safe than sorry...

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum