vivid mit Homebrew, apk, apt, MacPorts, Nix, pacman, scoop, winget installieren

Projektlinks

• Homepage

Befehle und Aliase

• vivid

Projektgeschichte

The vivid changelog records v0.1.0 as the initial version and v0.3.0 as the point where the project was renamed from `dircolors-hd` to `vivid`. That rename also marked the project more clearly as a theme-oriented alternative to classic `dircolors` workflows.

Subsequent releases filled in the practical pieces that make an `LS_COLORS` generator pleasant to package and use: direct RRGGBB colors, better filetype database handling, embedded default themes and config files, XDG config support, previewing, deterministic output, and additional community themes.

By the 0.9 and 0.11 series, vivid had become a maintained Rust CLI with a catalog of common themes, including popular terminal color schemes, and prebuilt release assets for multiple platforms.

Adoptionsgeschichte

vivid's adoption is tied to the spread of modern Rust command-line tools and highly customized shell prompts. The README explicitly names `ls`, `tree`, `fd`, `bfs`, and `dust` as consumers of `LS_COLORS`, which makes vivid useful beyond a single command.

Its theme collection and package availability made it attractive to users who wanted the same color language across file listings, search tools, and disk-usage tools without editing raw ANSI sequences.

Wie es verwendet wird

Users generate an `LS_COLORS` string from a named or custom theme and export it from their shell startup files. vivid also supports custom filetype databases and custom YAML themes under XDG-style configuration paths.

The separation between filetype database and theme is the core workflow: file classifications can be shared while colors are swapped independently.

Warum Paket-Nerds sich dafür interessieren

vivid is significant because it turns one of the messier Unix environment variables into declarative data. For package nerds, it is a small example of a modern Rust CLI improving an old shell convention without replacing the surrounding tools.

It also connects several popular CLI packages: `fd`, `bfs`, `dust`, `tree`, and GNU or BSD file-listing tools can all benefit once the environment variable is generated.

Zeitleiste

• v0.1.0: Initial version.
• v0.3.0: Project renamed to vivid from dircolors-hd.
• v0.4.0: Added direct RRGGBB color support and better filetype database handling.
• v0.6.0: Embedded default themes and config files, and added XDG_CONFIG_HOME support.
• v0.9.0: Added deterministic output work, more filetypes, and additional themes including Catppuccin variants.
• 2026: GitHub releases list v0.11.1 with signed multi-platform release assets.

Related projects

• vivid is conceptually related to GNU `dircolors`, but it chooses themeable YAML data rather than the traditional single generated database format.
• It is also related to tools that consume `LS_COLORS`, including `ls`, `tree`, `fd`, `bfs`, and `dust`.

Quellen

• batch input current_curation.config-file-location and current_curation.tags
• https://github.com/sharkdp/vivid
• https://github.com/sharkdp/vivid/blob/master/CHANGELOG.md
• https://github.com/sharkdp/vivid/releases
• https://manpages.ubuntu.com/manpages/noble/man1/vivid.1.html