Subject: bug#28334: closed (Re: bug#28334: A gnu extension for gnu grep)

From: [email-masked] (GNU bug Tracking System)
Date: Sun, 03 Sep 2017 01:41:02 +0000

Your bug report

#28334: A gnu extension for gnu grep

which was filed against the grep package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
28334: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=28334
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#28334: A gnu extension for gnu grep
From: Paul Eggert <[email-masked]>
To: Camion SPAM <[email-masked]>, [email-masked]
Date: Sat, 2 Sep 2017 18:40:40 -0700
List-Id: <debbugs-submit.debbugs.gnu.org>

It sounds like grep -Z does what you want, so I'm boldly closing this 
bug report.

Subject: A gnu extension for gnu grep
From: Camion SPAM <[email-masked]>
To: "[email-masked]" <[email-masked]>
Date: Sun, 3 Sep 2017 00:47:16 +0000 (UTC)
List-Id: <debbugs-submit.debbugs.gnu.org>

Hello, 
for the use with xargs -0, gnu find has a -print0 option allowing the user to process files even having the <LF> character in their name. however, in one wants to make à check on the content, this doesn't work anymore : One can write find <DIR> <CONDITIONS> -print0 | xargs -0 grep -l <REGEXP> | tr '\n' '\0' | xargs -0 ...to have de second xargs allows files with <SP> or other special characters in their names, but this won't work with files with <LF> in their name.
For this reason, I suggest we add a gnu --print0 option to grep (to be used with -l) which will separate the filenames produced with grep -l, with <NULL> characters instead of <LF> characters, in order to allow the correct processing of files with a <LF> in their names.

One might object that making a file with an <LF> character in it's name is stupid, but it is always possible to create one by mistake, juste with a wrong quote matching in shell commands or scripts.
Best regards, 
Camion