id       = "polybar"
name     = "Polybar"
homepage = "https://polybar.github.io"
# The project's own repository description.
description = "A fast and easy-to-use status bar"
# The SVG favicon from the project's own site.
icon     = "https://polybar.github.io/assets/favicon.svg"
executables   = ["polybar", "polybar-msg"]
# Polybar draws itself on X11 and its own README calls it a status bar for
# Linux desktops; there is no macOS or Windows build.
platforms = ["linux"]

[dotfiles]

# polybar(1), the project's own man page
# (https://polybar.readthedocs.io/en/stable/man/polybar.1.html), lists the
# search order for the config file:
#
#   $XDG_CONFIG_HOME/polybar/config
#   $XDG_CONFIG_HOME/polybar/config.ini
#   $HOME/.config/polybar/config
#   $HOME/.config/polybar/config.ini
#   $XDG_CONFIG_DIRS/polybar/config.ini
#   /etc/xdg/polybar/config.ini
#   /etc/polybar/config.ini
#
# — the user-level ones are $XDG_CONFIG_HOME/polybar with $HOME/.config as the
# fallback, which is exactly [configHome]. The directory rather than the two
# file names, because a user's bar is usually split across `include-file`
# fragments and scripts kept next to it. The last three entries are system
# paths outside the home directory.
paths = ["[configHome]/polybar/"]

# Bar geometry, module list, colours, fonts and the shell one-liners custom
# modules run. No account, no credential.
secret = []

# polybar-msg reloads a running bar, and polybar re-reads the file on restart
# rather than holding it open, so rewriting it mid-session is harmless.
side_effect = false

# No machine_lines: `monitor = ` names an X output such as HDMI-1, which is
# arguably per-machine, but polybar's own docs make it optional and a launch
# script usually fills it from `polybar --list-monitors` — so a rule on it
# would hold back a line most configurations do not have.