[bug #52137] unexpected behaviour when combining -I and -n

Update of bug #52137 (project findutils): Open/Closed:Open => Closed Fixed Release:None => 4.8.0 ___ Reply to this item at:

[bug #52137] unexpected behaviour when combining -I and -n

Update of bug #52137 (project findutils): Status:None => In Progress Assigned to:None => berny ___ Follow-up Comment #11: Bernhard, I

[bug #52137] unexpected behaviour when combining -I and -n

Follow-up Comment #10, bug #52137 (project findutils): James wrote in comment #8: > In issue 6, -L and -n are specified to interact such that the last-specified takes effect. The -I option is specified, but no interaction with -L or -n is called out. > > In issue 7, we have the previously

[bug #52137] unexpected behaviour when combining -I and -n

Follow-up Comment #9, bug #52137 (project findutils): (For those following by email only, the Savannah bug tracker entry for this bug is https://savannah.gnu.org/bugs/index.php?52137) ___ Reply to this item at:

[bug #52137] unexpected behaviour when combining -I and -n

Follow-up Comment #8, bug #52137 (project findutils): The approach (issue a warning without changing the current semantics of sequences of these options) seems good to me. I'd like to apply this patch basically as-is, with perhaps a couple of tweaks to the wording of the NEWS entry and the

[bug #52137] unexpected behaviour when combining -I and -n

Follow-up Comment #7, bug #52137 (project findutils): oops, good catch - missing "{...}" in the else case. Regarding the tests: I would try to avoid having so many one-line test files. Furthermore, I'm not very good in Tcl, so I propose to build up more shell based tests ... and have helper

[bug #52137] unexpected behaviour when combining -I and -n

Follow-up Comment #6, bug #52137 (project findutils): > I squashed the commits into one, and changed the following: > - use error() rather than fprintf(), I tried that first but it broke the testsuite because error() always outputs argv[0] and argv[0] will include the path when run from

[bug #52137] unexpected behaviour when combining -I and -n

Follow-up Comment #5, bug #52137 (project findutils): Thanks for the patches ... I also had already started something similar. I squashed the commits into one, and changed the following: - use error() rather than fprintf(), - factor out the outputting of the warning diagnostic into its own

[bug #52137] unexpected behaviour when combining -I and -n

Follow-up Comment #4, bug #52137 (project findutils): Hello, find attached a patch series to - improve documentation for conflicting options - make xargs display a warning on conflicting options - increase coverage for these options. cu Andreas (file #42093, file #42094, file #42095)

[bug #52137] unexpected behaviour when combining -I and -n

Follow-up Comment #3, bug #52137 (project findutils): Hello, agreed regarding addition of warning and doc-update. > "But I cannot see posix requiring that -I and -n must produce > strange results, so xargs could go beyond posix and produce > correct results in that case anyway." Actually POSIX

[bug #52137] unexpected behaviour when combining -I and -n

Follow-up Comment #2, bug #52137 (project findutils): It's neither documented nor does xargs perfom any checks if mutually-exclusive options are provided. So I think both should be fixed. But I cannot see posix _requiring_ that -I and -n _must_ produce strange results, so xargs could go beyond

[bug #52137] unexpected behaviour when combining -I and -n

URL: Summary: unexpected behaviour when combining -I and -n Project: findutils Submitted by: uli42 Submitted on: Thu 28 Sep 2017 10:37:17 AM UTC Category: xargs