Update of bug #62268 (group findutils):
Severity: 3 - Normal => 1 - Wish
_______________________________________________________
Follow-up Comment #2:
Another problem with this is that there are already things which affect find's
exit code. They don't necessarily cause find to exit immediately. But the
non-zero exit value serves to tell the caller that the output of find may have
bewn incorrect or incomplete.
Allowing for example "-exit 0" would hide those failures from the caller. So
I am not keen on this idea.
But the comparison with NetBSD is somewhat interesting. I wonder how
frequently the feature is actually used.
Meanwhile though, if you want to be able to do this kind of thing with GNU
find as-is, use -fprint -quit and check the file after find has exited.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?62268>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
