Summary
The whitaker-ls wrapper script generated by whitaker-installer passes --color never to cargo dylint list, which does not accept that flag. The command fails on every invocation.
Reproduction
$ whitaker-ls
error: unexpected argument '--color' found
Usage: cargo dylint list [OPTIONS]
For more information, try '--help'.
Generated wrapper (~/.local/bin/whitaker-ls):
#!/usr/bin/env bash
set -euo pipefail
export DYLINT_LIBRARY_PATH="/home/leynos/.local/share/whitaker/lints/nightly-2026-05-28/x86_64-unknown-linux-gnu/lib"
cargo dylint list --color never | awk -v suite="whitaker_suite" '$0 ~ "^" suite "([[:space:]]|$)" { print }'cargo dylint list --help on cargo-dylint 6.0.1 shows no --color option.
Note set -euo pipefail means the wrapper exits non-zero and prints nothing useful, so whitaker-ls is entirely unusable rather than merely noisy.
Impact
Minor on its own — but whitaker-ls is what the user's guide points at for confirming which suite libraries are installed, which is exactly the diagnostic one reaches for when the suite version is in question (see #331, #332). Losing it makes those investigations harder.
cargo dylint list works when invoked directly, so the workaround is to run that and filter manually.
Suggested fix
Drop --color never from the generated wrapper, or gate it on the installed cargo-dylint version if a colour override is wanted where supported.
Environment
cargo-dylint 6.0.1- toolchain
nightly-2026-05-28
- Linux (Rocky 10), wrapper freshly generated by
whitaker-installer
Summary
The
whitaker-lswrapper script generated bywhitaker-installerpasses--color nevertocargo dylint list, which does not accept that flag. The command fails on every invocation.Reproduction
Generated wrapper (
~/.local/bin/whitaker-ls):cargo dylint list --helpon cargo-dylint 6.0.1 shows no--coloroption.Note
set -euo pipefailmeans the wrapper exits non-zero and prints nothing useful, sowhitaker-lsis entirely unusable rather than merely noisy.Impact
Minor on its own — but
whitaker-lsis what the user's guide points at for confirming which suite libraries are installed, which is exactly the diagnostic one reaches for when the suite version is in question (see #331, #332). Losing it makes those investigations harder.cargo dylint listworks when invoked directly, so the workaround is to run that and filter manually.Suggested fix
Drop
--color neverfrom the generated wrapper, or gate it on the installedcargo-dylintversion if a colour override is wanted where supported.Environment
cargo-dylint6.0.1nightly-2026-05-28whitaker-installer