[BUG] unintended behavior when using "-1"

[borkd]

Checks

• I have read the troubleshooting section and still think this is a bug.

Describe the bug you encountered:

Thanks for fd, it comes in handy!

Attempts to use the shorthand -1 alias instead of --max-results with exec or batch exec are not prevented, and the operations will be performed on every object which matches the query instead of the first hit. Depending on what one was trying to achieve the impact of this can be quite significant.

The alias does not have the relevant conflicts_with

fd/src/cli.rs

Lines 513 to 522 in 93cdb26

	/// Limit the search to a single result and quit immediately.
	/// This is an alias for '--max-results=1'.
	#[arg(
	short = '1',
	hide_short_help = true,
	overrides_with("max_results"),
	help = "Limit search to a single result",
	long_help
	)]
	max_one_result: bool,

Using long option --max-results=1 would yield immediate abort and explanation that options conflict:

fd/src/cli.rs

Lines 20 to 30 in 93cdb26

	#[derive(Parser)]
	#[command(
	name = "fd",
	version,
	about = "A program to find entries in your filesystem",
	after_long_help = "Bugs can be reported on GitHub: https://github.com/sharkdp/fd/issues",
	max_term_width = 98,
	args_override_self = true,
	group(ArgGroup::new("execs").args(&["exec", "exec_batch", "list_details"]).conflicts_with_all(&[
	"max_results", "has_results", "count"])),
	)]

Finally -1 overrides_with --max-results, but not the other way around so fd --max-results=1 -1 -X prog query will launch prog against all objects matching query.

Describe what you expected to happen:

Consistent behavior: if mixing max-results with exec-type functions is refused, same should be true for aliases.

What version of fd are you using?

8.7.0

Which operating system / distribution are you on?

Linux

[emikitas]

Hi,
I can take this. I reproduced this bug and saw it doesn't reproduce in version 8.3.1.