GNU bug report logs - #71321
30.0.50; M-x grep: not recognizing well files with colon

Previous Next

Full log

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

From: Dmitry Gutov <dmitry <at> gutov.dev>
To: Eli Zaretskii <eliz <at> gnu.org>, Jim Porter <jporterbugs <at> gmail.com>
Cc: 71321 <at> debbugs.gnu.org, bugs <at> gnu.support
Subject: Re: bug#71321: 30.0.50; M-x grep: not recognizing well files with
 colon
Date: Mon, 3 Jun 2024 15:03:56 +0300

On 03/06/2024 14:43, Eli Zaretskii wrote:
>> Date: Sun, 2 Jun 2024 21:17:02 -0700
>> Cc:71321 <at> debbugs.gnu.org
>> From: Jim Porter<jporterbugs <at> gmail.com>
>>
>> On 6/2/2024 3:02 AM, Eli Zaretskii wrote:
>>> Improved how?  Can you suggest how to distinguish between ":39:" and
>>> ":13:" in the Grep output, when searching where the file name ends and
>>> the line number and the following test starts?
>> M-x grep and friends should already be doing the right thing: when
>> supported, it passes "--null" to "grep", which changes the output so
>> that it separates the file name from the line number using a NUL
>> character. The regexps in grep.el can then detect that output and parse
>> it correctly.
> I know, but since Jean reported this, his Grep evidently doesn't do
> that.  So I asked how to do better in that case.

Perhaps he had customized grep-template, so that the --null flag is not 
there.

Previous Next

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