Update of bug #39897 (project findutils):
Status: None => Need Info
Assigned to: None => jay
_______________________________________________________
Follow-up Comment #1:
One of the reasons this has not previous been implemented is that the order in
which find examines the file system is only partly defined (i.e. start points
are examined in order, either depth-first or in preorder). Hence using a
limit of say 100 would provide almost no control over which 100 results are
generated.
A second reason is that there is ambiguity over what a "result" is. Consider
this for example:
find / -name foo -fprint /tmp/foos , -name bar -fprint /tmp/bars -max_count
200
What behaviour should one expect?
The -quit predicate suffers a bit from the first problem but not when the
second (since it takes effect as soon as it is reached).
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?39897>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
