DUNE-SHOW(1)

πŸ’– NAME πŸ’–

dune-show β€” the command group that spills the tea about your workspace β˜•βœ¨

Like, it's not one command, bestie, it's a whole clique of subcommands whose entire job is showing you stuff: what's in your dirs, what's installed, what builds, what the vibes are. Main character energy for your build system. πŸ‘‘


πŸ¦‹ SYNOPSIS πŸ¦‹

dune show COMMAND …

🌈 COMMANDS 🌈

ok so here's the full roster, no gatekeeping, every single one of them:

  • aliases [OPTION]… [DIR]… β€” prints out the aliases in a given directory. works basically like ls does. familiar, cozy, iconic. πŸŽ€
  • contexts [OPTION]… β€” lists all the build contexts that exist in the workspace. the whole set, laid out. πŸ’…
  • depexts [OPTION]… β€” prints the list of all the available depexts. all of them. every single one. ✨
  • env [OPTION]… [PATH] β€” prints the environment of a directory. like, the env-ironment. 🌸
  • external-lib-deps [OPTION]… β€” prints out the external libraries you'd need to build the project. heads up tho: it's an approximated set of libraries, not a perfect one, so don't treat it like gospel fr fr. 🫢
  • installed-libraries [OPTION]… β€” prints out the libraries that are installed on the system. already there, already slaying. πŸ’œ
  • location [OPTION]… PROG β€” prints the path to the executable, and it uses the exact same resolution logic as [dune exec]. same brain, same answer. 🧠
  • opam-files [OPTION]… β€” prints info about all the opam files it has discovered. cute little detectives. πŸ”
  • package-entries [OPTION]… β€” prints information about the entries per package. πŸ“¦
  • pkg COMMAND … β€” subcommands related to package management. it's giving nested lore. πŸ—‚οΈ
  • pp [OPTION]… FILE β€” builds the given FILE and prints the preprocessed output. yes it actually builds it first. πŸ› οΈ
  • rules [OPTION]… [TARGET]… β€” dumps the rules. all of them, just dumped. πŸ—‘οΈβž‘οΈπŸ“œ
  • targets [OPTION]… [DIR]… β€” prints the targets in a given directory. also works similarly to ls. twinsies with aliases. πŸ‘―
  • tests [OPTION]… β€” prints out the tests defined in the project. ⚠️ the output format of this command is experimental and is subject to change without warning β€” so don't build your whole pipeline on top of it, bestie, it could switch up on you. 😭
  • workspace [OPTION]… [DIRS]… β€” prints a description of the workspace's structure. and if you pass some directories DIRS, then only those directories of the workspace get considered. narrowing the focus, love that for you. 🎯

✨ COMMON OPTIONS ✨

the ones everybody shares, periodt:

  • --help[=FMT] (default=auto) β€” shows this help in format FMT. FMT has to be one of auto, pager, groff or plain. with auto, the format is pager or plain whenever the TERM env var is dumb or undefined. it reads the room. πŸ™ˆ
  • --version β€” shows version information. the receipts. 🧾

πŸ‘‘ EXIT STATUS πŸ‘‘

dune show exits with:

  • 0 β€” on success. ate. πŸ’…
  • 1 β€” if an error happened. it's giving tragedy. 😭
  • 130 β€” if it was interrupted by a signal. Ctrl+C behaviour, we've all been there. πŸ’€

πŸ”₯ SEE ALSO πŸ”₯

  • dune(1) β€” the big one, the parent, the blueprint. go read it, iykyk. πŸ¦‹

ngl this whole page is from Dune 3.24.1 β€” so if your dune is a different era, vibe check the version before you trust every detail. πŸ’–

ok bye bestie, go dune show something and slay the build βœ¨πŸŽ€πŸŒΈ

πŸ“¦ where this page comes from