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

I have installed a modified version of the patch (1dcdf3de8e27cc130968891ee5a529a461a248da), updated in the ways you suggested. On Sat, Nov 2, 2024 at 9:24 AM Bernhard Voelker wrote: > > Hi James, > > thanks, technically this patch fixes it, yet I think it deserves some more > love before pushin

[PATCH] find: -exec is terminated by + only if the prior arg is exactly '{}'

A "+" only terminates -exec when it immediately follows an argument which is exactly "{}" (and not, for example, "{}x"). This fixes Savannah bug 66365. * NEWS: explain this change. * doc/find.texi: update one place which omitted the '{}' before '+'. * find/parser.c (insert_exec_ok): consider + to

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

Hi James, thanks, technically this patch fixes it, yet I think it deserves some more love before pushing. First of all, this patch does not cleanly apply. $ git am /tmp/x.patch Applying: Fix Savannah bug 66365. error: git diff header lacks filename information when removing 1 leading pa