[bug #66365] find -exec treats + as special when it shouldn't

2024-10-31 Thread James Youngman
Follow-up Comment #2, bug #66365 (group findutils): Because GNU find currently rejects these commands with the error shown in Geoff's comment, I'm not expecting there to be a substantial problem with backward incompatibility. That is, I doubt that anybody is likely to be relying on GNU find rejec

[bug #66365] find -exec treats + as special when it shouldn't

2024-10-31 Thread James Youngman
Follow-up Comment #4, bug #66365 (group findutils): I think the attached patch should fix this. (file #56587) ___ Additional Item Attachment: File name: 0001-find-Fix-Savannah-bug-66365.patch Size: 4KiB

Re: [bug #66365] find -exec treats + as special when it shouldn't

2024-10-31 Thread James Youngman
>From e7641882e3ef373b6c58bcf27fbc49269e2541f3 Mon Sep 17 00:00:00 2001 From: James Youngman Date: Thu, 31 Oct 2024 15:06:02 + Subject: [PATCH] [find] Fix Savannah bug 66365. A "+" only terminates -exec when it immediately follows an argument which is exactly "{}". --- find/parser.c

[bug #66365] find -exec treats + as special when it shouldn't

2024-10-31 Thread James Youngman
Update of bug #66365 (group findutils): Release:None => 4.2.12 ___ Follow-up Comment #3: This bug was introduced in findutils 4.2.12, which is the release which added support for "+".

[bug #66365] find -exec treats + as special when it shouldn't

2024-10-31 Thread James Youngman
Update of bug #66365 (group findutils): Severity: 3 - Normal => 4 - Important Assigned to:None => jay ___ Reply to this item at:

[bug #66365] find -exec treats + as special when it shouldn't

2024-10-31 Thread James Youngman
Follow-up Comment #1, bug #66365 (group findutils): Implicit in Geoff's comment is that the rules for terminating the expression are different for the ";" and "+" cases. The full wording from the standard (IEEE Std 1003.1-2024) is: -exec utility_name [argument ...] ; -exec utility_name [argumen