|
From: | Eric Blake |
Subject: | bug#32704: Can grep search for a line feed and a null character at the same time? |
Date: | Tue, 11 Sep 2018 12:39:54 -0500 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.0 |
On 9/11/18 12:14 PM, Paul Eggert wrote:
On 9/11/18 10:03 AM, Eric Blake wrote:maybe we really do have a bug - when -z is in effect, I'd expect NUL, rather than newline, to be the byte that separates separate patterns in the pattern argumentYou're right, I think it's a bug that grep -zf FILE uses newline separators in FILE. It should use NUL separators.This cannot be done for NUL bytes in command-line patterns, though, since command-line arguments cannot contain NUL bytes.
Indeed. But that merely means that on the command line, when -z is in effect, you can't specify multiple patterns (but instead have to use -f FILE if that's what you really want). Meanwhile, the effect on being able to match a literal newline would be observable from either the command line or -f FILE.
-- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org
[Prev in Thread] | Current Thread | [Next in Thread] |