GNU bug report logs -
#9226
23.3; [rgrep]; (matches found) ?
Previous Next
Reported by: Dave Abrahams <dave <at> boostpro.com>
Date: Wed, 3 Aug 2011 01:42:02 UTC
Severity: normal
Found in version 23.3
Done: Juri Linkov <juri <at> jurta.org>
Bug is archived. No further changes may be made.
Full log
Message #20 received at 9226 <at> debbugs.gnu.org (full text, mbox):
On Wed, Aug 17, 2011 at 16:52, Dave Abrahams <dave <at> boostpro.com> wrote:
>
> on Wed Aug 10 2011, Juri Linkov <juri-AT-jurta.org> wrote:
>
>> So to never lie to the users and determine reliably
>> the status we could use the following logic:
>>
>> If status is 0 and the output is not empty:
>> Grep finished (matches found)
>>
>> Otherwise:
>> Grep exited with status %d
>>
>> These changes completely remove the case of status 1 that displayed
>> "finished with no matches found", and also remove the word "abnormally"
>> from the message of remaining cases, because we can't reliably determine
>> the case of "no matches found" by checking status 123 of a command line
>> that contains "xargs".
>
> Sounds like an improvement to me.
Is it the status of the grep program that is shown, or? Maybe this
should be clarified?
This bug report was last modified 13 years and 252 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.