On 1/26/21 5:47 AM, Stuart Henderson wrote:
> On 2021/01/25 00:53, Sebastian Benoit wrote:
>> Sebastian Benoit(be...@openbsd.org) on 2021.01.25 00:27:05 +0100:
>>> Theo de Raadt(dera...@openbsd.org) on 2021.01.24 16:01:32 -0700:
>>>> Stuart Henderson <s...@spacehopper.org> wrote:
>>>>
>>>>> On 2021/01/24 12:10, Theo de Raadt wrote:
>>>>>> I completely despise that the option is called "--null".
>>>>>>
>>>>>> Someone was a complete idiot.
>>>>> gnu grep has both --null and -z for this (why do they do that?!).
>>>>> If it's added as --null it should be added as -z too.
>>>>>
>>>>> Looking at Debian codesearch most things using it as --null use other
>>>>> long options that we don't have. Maybe just adding as -z would be
>>>>> enough. It does seem a useful and fairly widely supported feature.
>>>> Yes, maybe just add -z.
>>> Actually it's "-Z, --null". The lowercase -z in gnu grep is
>>>
>>> -z, --null-data
>>> Treat input and output data as sequences of lines, each
>>> terminated by a zero byte (the ASCII NUL character) instead of
>>> a newline. Like the -Z or --null option, this option can be
>>> used with commands like sort-z to process arbitrary file
>>> names.
>> And we already have -z for "force grep to behave as zgrep".
> sigh.. OK I guess we are better skipping the short flag and just use --null
>
>> Diff below with tedu@ suggestion and changed manpage text.
> ok with me. if I was committing I would whine about the stupid flag in
> commit log ;)
>
> [snip]
Why is a short flag not being included? '-z' and '-0' are both available in our
grep.
Jordan
