ZVM-BUG(1)

πŸ“¦ version 0.9.4, in nixpkgs unstable

πŸ’… ZVM-BUG(1) β€” like, the whole manual, bestie

okay so this is the manual page for zvm-bug from the ZVM-BUG(1) family of docs β€” sit down, hydrate, and let me tell you about the one command that turns "it's broken 😭" into an actual, fillable bug report πŸŽ€


✨ NAME ✨

zvm-bug β€” start a ZVM bug report πŸ›πŸ’–


🌸 SYNOPSIS 🌸

zvm bug [--print]

πŸ¦‹ DESCRIPTION πŸ¦‹

It opens a prefilled issue form for the ZVM repository in your browser. Periodt. 🌈 The form comes with a report template and a collected description of the environment ZVM is running in β€” like it did the homework for you, no cap πŸ“šβœ¨

Important vibe check: zvm does not submit the report for you. You fill in what you did, what happened, and what you expected, you review the collected environment, and then you submit the issue yourself. Main character energy only πŸ‘‘πŸ’…

The collected environment includes:

  • the ZVM version
  • the target operating system and architecture
  • the ZVM base directory
  • the values of the ZVM_* environment variables
  • the configured mirror list and version-map URLs
  • the installed Zig versions
  • the selected Zig and ZLS versions
  • the host kernel and distribution

like… it's thorough. it's giving "receipts" 🧾πŸ”₯


πŸ™ˆ ANONYMIZATION πŸ™ˆ

Paths inside the user's home directory are reported relative to ~, so the report doesn't name the account it came from 🫢 cute, right? Paths outside the home directory are reported as they are. no filter, no changes πŸ’€

Mirror-list and version-map URLs distributed with ZVM are reported verbatim ⭐

A URL the user configured is replaced by a short digest, written as custom sha256:digest πŸ”

okay bestie, listen β€” the digest is a correlation tag, not a secret. A URL is drawn from a small enough set of candidates that hashing guesses recovers it, so the digest only serves to distinguish one custom source from another without publishing it. Report contents should still be reviewed before submitting πŸŽ€πŸ‘€

πŸ’œ OPTIONS πŸ’œ

  • --print β€” Print the report URL instead of opening a browser. Useful on machines with no browser, such as a remote shell or a container πŸ–₯️✨

🧚 BROWSER SELECTION 🧚

If BROWSER is set, it is run with the report URL as its argument 🫑

Otherwise the platform handler is used:

  • open on macOS 🍎
  • cmd /c start on Windows πŸͺŸ
  • xdg-open, www-browser, or x-www-browser elsewhere 🐧

On other systems, a browser is only attempted when DISPLAY or WAYLAND_DISPLAY is set πŸ‘€

When no browser can be started, the URL is printed instead β€” no drama, it still slays πŸ’…


🌟 ENVIRONMENT 🌟

  • BROWSER β€” Command used to open the report URL 🌐
  • DISPLAY, WAYLAND_DISPLAY β€” Presence of either indicates a display server that can show a browser πŸ–ΌοΈ

πŸ”₯ EXAMPLES πŸ”₯

zvm bug
zvm bug --print

that's it. that's the whole thing. ate and left no crumbs πŸ“


πŸ‘‘ SEE ALSO πŸ‘‘

zvm(1), zvm-version(1), zvm-upgrade(1)

go read those too, they're iconic, iykyk πŸ’–


✿ and that's the tea, bestie ✿ this page is from ZVM v0.9.4, dated August 2026 β€” take care of her, she's a whole queen πŸŽ€πŸ’…βœ¨

πŸ“¦ where this page comes from
  • nixpkgs unstable: zvm 0.9.4
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms