bug#22945: Surprising behaviour (bug?) of zgrep in combination with the -f option and process substitutions

[Paul Eggert]

Jim Meyering wrote:
> Might be tricky to portably transform that NUL byte into something we
> can embed in a command-line-specified search string. Is there even a
> notation for that? I don't think so.
>
> But NUL problems aside, this also should work, requiring alternation
> in the regexp derived from input with two or more lines, but then
> we'll have to escape embedded '|' bytes, too:

How about the attached patch instead? It uses a bigger hammer, which should 
address both issues.

0001-zgrep-with-f-SPECIAL-read-SPECIAL-just-once.patch
Description: Text Data