[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #65895] Expression order matters?
From: |
raf |
Subject: |
[bug #65895] Expression order matters? |
Date: |
Wed, 17 Jul 2024 20:17:35 -0400 (EDT) |
Follow-up Comment #5, bug #65895 (group findutils):
Sorry I didn't make myself clear enough. I wasn't suggesting that "find .
-delete" stop working. I was suggesting that it become an error for -delete to
be followed by one or more pure predicate options (e.g. -name) but no
side-effect options (e.g. -exec). It's not the same thing, since such commands
would never have been intentional or valid. Even if someone did want to delete
all files and list a subset of them (for example), they would find that that
didn't work, presumably because the files are deleted before their names are
checked (I just tried "touch a b c; find . -delete -name a" and there was no
output but I expected it to output "./a" if there was any point in having pure
predicate options after -delete).
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?65895>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [bug #65895] Expression order matters?,
raf <=