[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #60383] [feature-request] let find read files from stdin or file.

From: James Youngman
Subject: [bug #60383] [feature-request] let find read files from stdin or file.
Date: Wed, 14 Apr 2021 05:20:30 -0400 (EDT)
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36

Follow-up Comment #3, bug #60383 (project findutils):

We cannot use //x as a way to escape x, because in POSIX path names matching
//[^/] are `special` and have an implementation-defined significance, which
`find` cannot know (find is intended to run also on non-GNU systems).

The difficulties around -H/-L/-P could be resolved I think by making --file0
incompatible with -H.  That is, making it an error to specify both.

Other things we should document if we implement this option:

1. The seek position on the named file at the time find exits (normally, with
-quit or in any other way) is not specified.
2. If --file0 is specified, no (other) starting points may be specified on the
command line
3. If a file is listed more than once in the input file it is unspecified
whether it is visited more than once (my motivation here is that we may need
to worry about the interaction between this and symlink loop detection)
4. If the file is mutated during the operation of find, the result is
5. The effect of empty records (i.e. \0\0) is unspecified.

By "unspecified" here I mean, may not work, may not do any specific thing, and
this may change from platform to platform or findutils release to release.


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]