`--exec-batch` does not mention it should be last

[orlp]

--exec's documentation has the following two sentences:

All positional arguments following --exec are considered to be arguments to the command - not to fd. It is therefore recommended to place the '-x'/'--exec' option last.

I believe the same thing applies to --exec-batch, but its documentation is missing those two sentences.

[nettyso]

I just ran into this and it's funny it's the first GH issue I see. It's not clear how to end the -x command, I imagine most people try single quotes to no avail.

Personally the confusion comes from the first line of --help

USAGE:
    fd [FLAGS/OPTIONS] [<pattern>] [<path>...]

This explicitly says that OPTIONS like -x must precede the pattern and path, but then it's impossible to provide a pattern or path in combination with -x? In the project README all of the examples shown that use -x do not use a path or pattern, so maybe this is true?

[nettyso]

Kinda distracted rn but if I can remember to make a PR in the next day I'll propose changing help text to

USAGE:
    fd [FLAGS/OPTIONS] [<pattern>] [<path>...]
    fd [<pattern>] [FLAGS/OPTIONS] [<path>...]
    fd [<pattern>] [<path>...] [FLAGS/OPTIONS]

...

All positional arguments following --exec are considered to be arguments to the command - not to fd. Using quotes will not prevent this. It is therefore required to place the '-x'/'--exec' option last, after your (optional) pattern and/or path.

[tavianator]

@nettyso You can use ; to terminate the command, just like with find. For example:

tavianator@graphene $ fd -x echo file: \; . src
file: src/regex_helper.rs
file: src/dir_entry.rs
file: src/walk.rs
...