Popular: Data updated November 21, 2026

Categories

Internet1,421
Communication329
Audio & video938
Graphics & design566
Office & productivity1,184
Developer tools3,288
AI tools610
Security & privacy408
System tools3,194
Games545
Education & science242
Network & IT294

usage 7.3.0 download

A specification for CLIs

This is an older version. The current version is 7.4.0. usage 7.4.0 · Released:

Installer files 7.3.0

ArchitectureTypeScopeFile sizeDownloadSHA256
64-bit ZIP → Portable — — github.com VirusTotal
ARM64 ZIP → Portable — — github.com VirusTotal

Link and SHA256 come from the Windows Package Manager community manifest. Compare the hash of the downloaded file before running it.

Release notes

Added
- (lib) New usage_rs::completion::Completion subcommand, available with the completions feature (#1624, @jdx). Until now each tool wrote its own completion command: some had --install, while others printed a script for the user to redirect by hand. You can now mount the shared command instead:
use usage_rs::completion::Completion;
#[derive(Subcommands)]
enum Commands {
/// Generate shell completions
Completion(Completion),
}
// in the run function:
completion.run("ex", &mut std::io::stdout())?;
Any tool that mounts it gets these commands:
ex completion fish # print the script, e.g. `ex completion fish | source`
ex completion fish --install # write it where fish looks for it
ex completion fish --install --force # also replace a file usage did not generate
- Shells: bash, elvish, fish, nu/nushell, powershell/pwsh and zsh are accepted. Any other shell name fails to parse.
- Flags: --force requires --install.
- Scripts: The scripts are the short callback scripts. They contain no spec and don't need the usage binary. On every Tab they ask the installed tool for candidates, so they stay correct when the tool is upgraded.
- Installing: --install never edits a startup file. If a shell needs a line added once, the command prints that line after the install path.
- Errors: Completion::run returns Error::Install or Error::Output. A closed pipe (for example ex completion zsh | head) is not treated as an error.
- Testing: Completion::run_in takes an explicit Env, so tests can install without touching the real home directory.
The Rust completions guide (docs/rust/completions.md) now uses Completion in place of the hand-written example.

💚 Sponsor usage
usage is built and maintained by @jdx, an open source developer at entire.io, the title sponsor of his open source work.
If usage powers CLI specs, docs, or completions for a tool you maintain or use, please consider becoming an individual or company sponsor. Your support funds ongoing development and helps keep usage fast, free, and independent.

https://github.com/jdx/usage/releases/tag/v7.3.0

Most popular in Terminals & CLI tools

See all
  1. PowerShellPowerShell is a cross-platform task automation solution made up of a command-line shell, a scripting language, and a configuration management framework. PowerShell runs on Windows, Linux, and macOS.
  2. QPDFQPDF is a command-line tool and C++ library that performs content-preserving transformations on PDF files.
  3. Oh My PoshPrompt theme engine for any shell
  4. Microsoft Azure CLIThe Azure command-line interface (Azure CLI) is a set of commands used to create and manage Azure resources. The Azure CLI is available across Azure services and is designed to get you working quickly with Azure, with an emphasis on automation.
  5. yqyq is a portable command-line YAML, JSON, XML, CSV and properties processor.
  6. fzfA general-purpose command-line fuzzy finder
  7. AlacrittyAlacritty is a free and open-source GPU accelerated terminal emulator focused on performance and simplicity.
  8. PuTTYA free implementation of SSH and Telnet for Windows and Unix platforms, along with an xterm terminal emulator.
  9. cURLCommand line tool and library for transferring data with URLs
  10. TabbyA terminal for a more modern age.

More from jdx

See all

Tags

Share