[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
problem with recent change to grep-regexp-alist
From: |
Emanuele Giaquinta |
Subject: |
problem with recent change to grep-regexp-alist |
Date: |
Sat, 6 Aug 2005 12:34:01 +0200 |
User-agent: |
Mutt/1.5.9i |
Hi,
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).
Emanuele Giaquinta
- problem with recent change to grep-regexp-alist,
Emanuele Giaquinta <=
Re: problem with recent change to grep-regexp-alist, Stefan Monnier, 2005/08/09