--uninstall prompts for config removal when stdin is a TTY. Running the
test from an interactive terminal caused it to block on read. Feeding
/dev/null forces the non-interactive path without changing behaviour.
Show only the binary(s) actually present in the clipboard row label,
and use a yellow ✔ (instead of green) when only xclip is found so the
degraded state stands out from a fully-satisfied check.
All paths printed to the user in --help, --install, and --uninstall
now display as ~/... when the path falls under $HOME, and as a full
absolute path otherwise. Actual file operations continue to use the
original absolute paths unchanged.
- Resolve all paths via $XDG_CONFIG_HOME, $XDG_DATA_HOME, and
$XDG_RUNTIME_DIR with conventional fallbacks (~/.config,
~/.local/share, /tmp); BIN_DIR stays ~/.local/bin (no XDG standard)
- Add --uninstall: removes symlink, desktop entry, and data dir with
colored per-step output; prompts to remove config when interactive,
skips silently when not; post-run verification reports any failures
- Warn in --check-deps and --install when only xclip is present —
xclip operates through XWayland and can be unreliable on Wayland
- Normalize dependency messages to package names (wl-clipboard, xclip)
- Update README: XDG paths in install steps, --uninstall in usage,
xclip advisory in prerequisites
- Fix test sandbox: export XDG_CONFIG_HOME and XDG_DATA_HOME so the
overridden HOME is respected; add install (test 15) and uninstall
(test 16) coverage; add cp and ln to mocked tool set
rootiest
