id       = "waybar"
name     = "Waybar"
homepage = "https://github.com/Alexays/Waybar"
description = "Highly customizable Wayland bar for Sway and Wlroots based compositors."
executables   = ["waybar"]
platforms = ["linux"]

[dotfiles]

# waybar(5) lists the directories it searches for the file named `config` or
# `config.jsonc`, in order:
#
#   $XDG_CONFIG_HOME/waybar/
#   ~/.config/waybar/
#   ~/waybar/
#   /etc/xdg/waybar/
#
# The first two are the same directory under two names, which is [configHome];
# on Linux, the only platform Waybar runs on, that resolves to $XDG_CONFIG_HOME
# with ~/.config as the fallback, exactly as the man page has it. The ~/waybar
# fallback below it is the third place and is written literally. /etc/xdg is
# system-wide and out of scope.
#
# The stylesheet sits in the same directory: waybar(5) says "The visual display
# elements for waybar use a CSS stylesheet, see waybar-styles(5)", and
# style.css is found beside the config. Naming the directory covers the config,
# the stylesheet and the module snippets a user splits them into.
paths = [
  "[configHome]/waybar/",
  "~/waybar/",
]

# Nothing in the directory is a credential. A module that needs one — a weather
# or mail module — runs `exec` against a script the user wrote, and the script
# is where any token would be.
secret = []

# No machine_lines. The module list, the format strings, the icons and the
# stylesheet are exactly what a user wants on the next machine; the one thing
# that is arguably machine-bound, an output name like `DP-1` in a bar's
# `output` field, is a single optional key and holding it back would be a guess
# about a multi-monitor setup rather than a fact about the file.