Unable to run `cargo run --timings`

[lomirus]

cargo run --timings worked fine initially.

But once the following code was added to ​config.nu, cargo run --timings stopped working:

source "nu_scripts/custom-completions/cargo/cargo-completions.nu"

and produced this error:

Error: nu::parser::missing_flag_param

  × Missing flag argument.
   ╭─[entry #2:1:13]
 1 │ cargo build --timings
   ·             ────┬────
   ·                 ╰── flag missing string argument
   ╰────

[fdncred]

I'd guess it's because there is no --timings parameter in the cargo build custom completion.

nu_scripts/custom-completions/cargo/cargo-completions.nu

Lines 68 to 107 in 365b883

	# Compile the current package
	export extern "cargo build" [
	--package(-p): string@"nu-complete cargo packages" # Build only the specified packages
	--workspace # Build all members in the workspace
	--exclude: string@"nu-complete cargo packages" # Exclude the specified packages
	--lib # Build the package's library
	--bin: string@"nu-complete cargo bins" # Build the specified binary
	--bins # Build all binary targets
	--example: string@"nu-complete cargo examples" # Build the specified example
	--examples # Build all example targets
	--test: string # Build the specified integration test
	--tests # Build all targets in test mode that have the test = true manifest flag set
	--bench: string # Build the specified benchmark
	--benches # Build all targets in benchmark mode that have the bench = true manifest flag set
	--all-targets # Build all targets
	--features(-F): string@"nu-complete cargo features" # Space or comma separated list of features to activate
	--all-features # Activate all available features of all selected packages
	--no-default-features # Do not activate the default feature of the selected packages
	--target: string # Build for the given architecture.
	--release(-r) # Build optimized artifacts with the release profile
	--profile: string@"nu-complete cargo profiles" # Build with the given profile
	--ignore-rust-version # Ignore `rust-version` specification in packages
	--timings: string # Output information how long each compilation takes
	--target-dir: path # Directory for all generated artifacts and intermediate files
	--out-dir: path # Copy final artifacts to this directory
	--verbose(-v) # Use verbose output. May be specified twice for "very verbose" output
	--quiet(-q) # Do not print cargo log messages
	--color: string@"nu-complete cargo color" # Control when colored output is used
	--message-format: string # The output format for diagnostic messages
	--build-plan # Outputs a series of JSON messages to stdout that indicate the commands to run the build
	--manifest-path: path # Path to the Cargo.toml file
	--frozen # Require Cargo.lock and cache are up to date
	--locked # Require Cargo.lock is up to date
	--offline # Run without accessing the network
	-Z: any # Unstable (nightly-only) flags to Cargo, see 'cargo -Z help' for details
	-h, --help # Print help information
	--jobs(-j): number # Number of parallel jobs to run
	--future-incompat-report # Displays a future-incompat report for any future-incompatible warnings
	]

[lomirus]

Actually, the --timings parameter does exist in the completion file, specifically on line 90 @fdncred.

nu_scripts/custom-completions/cargo/cargo-completions.nu

Line 90 in 365b883

--timings: string # Output information how long each compilation takes

After multiple tests with different command variations in both completion-enabled and completion-disabled environments, I found that neither cargo build --timings nor cargo build --timings=html works—likely for different reasons:

• cargo build --timings fails:

In the original cargo build --timings[=<FMTS>] command, FMTS is an optional parameter, but the completion file doesn't mark it as optional (I'm not sure if NuShell supports this syntax).

• cargo build --timings=html fails:

In NuShell, cargo build --timings=html seems to be forcibly interpreted as cargo build --timings html, but the cargo command doesn't support this syntax, resulting in an error.

[fdncred]

ok, --timings: string means that it needs an argument and not a flag

In NuShell, cargo build --timings=html seems to be forcibly interpreted as cargo build --timings html, but the cargo command doesn't support this syntax, resulting in an error.

ya, it's probably interpreted that way.