[bug #52409] `find -print0 -name ...` ignores `-name ...`

2017-11-14 Thread anonymous
Follow-up Comment #2, bug #52409 (project findutils): Ah makes sense! Thanks for the thorough explanation -- didn't realize `print` was considered a predicate and thought it just controlled the final output. This can be closed -- apparently I can't do that since I posted anonymously. __

[bug #52409] `find -print0 -name ...` ignores `-name ...`

2017-11-14 Thread Dale Worley
Follow-up Comment #1, bug #52409 (project findutils): Actually, this is a usage error: -print is an action as well as a predicate. In particular, it takes effect when it is executed *in order* among the predicates. So if you execute find . -name '*.c' -print find will, for each file name, fir

[bug #52409] `find -print0 -name ...` ignores `-name ...`

2017-11-14 Thread anonymous
URL: Summary: `find -print0 -name ...` ignores `-name ...` Project: findutils Submitted by: None Submitted on: Tue 14 Nov 2017 11:46:44 PM UTC Category: find Severity:

[bug #42985] find reports "No such file or directory" when executing rm

2017-11-14 Thread James Youngman
Follow-up Comment #9, bug #42985 (project findutils): > find $(pwd) . -mindepth 1 -maxdepth 1 -regex $cpat -prune -o -exec rm -rfv {} \+ >/dev/null 2>../error.log The documentation explains why you should not do that. 9.3 Cleaning Up === This section gives examples of removing unwan

Re: Bug?

2017-11-14 Thread James Youngman
Please provide more details on the failure.

Re: Missing bits of regexprops.texi

2017-11-14 Thread James Youngman
Thanks for reporting this bug. The attached patches, which I plan to submit shortly, fix the problem. On Thu, Oct 26, 2017 at 9:17 AM, Reuben Thomas wrote: > The documentation as generated for findutils refers to "ed" syntax, > but does not define it. ("posix-basic" is given as a synonym for >