POLYBAR(1)

πŸ’… POLYBAR(1) β€” the polybar manual, bestie edition ✨

Okay so real talk: this is the manual page for polybar, aka the polybar user manual. If you've ever wanted a status bar that's actually cute and doesn't require you to sell your soul to shell scripting, this is your moment. Let's get into it 🫢


🌸 NAME 🌸

polybar β€” a fast and easy-to-use tool status bar. That's literally the whole vibe. No cap.


πŸ¦‹ SYNOPSIS πŸ¦‹

polybar [OPTIONS]... [BAR]

πŸŽ€ DESCRIPTION πŸŽ€

So polybar's whole thing is helping you build beautiful and highly customizable status bars for your desktop environment β€” and the best part? You do not need a black belt in shell scripting to pull it off. It's giving accessible icon behavior, honestly. πŸ’…

And here's a lil detail: if the BAR argument isn't provided and your configuration file only contains one bar definition, polybar will just go ahead and display that bar for you. Convenient, right? Obsessed.


✨ OPTIONS ✨

Every single flag, bestie. No skips, no skips, periodt. πŸ‘‘

  • -h, --help β€” display help text and exit. The classic "help me help you" move.
  • -v, --version β€” display build details and exit. Perfect for when you need to know what you're working with.
  • -l, --log=LEVEL β€” set the logging verbosity. The default is notice. LEVEL has to be one of: error, warning, notice, info, trace. Pick your chaos level wisely πŸŒ€
  • -q, --quiet β€” be quiet. And yes, this will override -l. It said what it said πŸ’€
  • -c, --config=FILE β€” specify the path to the configuration file. By default, the config file is loaded from:
    • $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 (only if XDG_CONFIG_DIRS is not set)
    • /etc/polybar/config.ini
  • -r, --reload β€” reload the application when the config file has been modified. Live your best hot-reload life πŸ”₯
  • -d, --dump=PARAM β€” print the value of the specified parameter PARAM in the bar section and exit. A little peek behind the curtain, iykyk.
  • -m, --list-monitors β€” print list of available monitors and exit. If some monitors are cloned, this will exclude all but one of them. And if polybar was compiled with RandR monitor support, only monitors are listed and not physical outputs. Important distinction, bestie πŸ–₯️
  • -M, --list-all-monitors β€” print list of all available monitors and exit. This includes cloned monitors as well as both physical outputs and RandR monitors (if supported). Only the names listed here can be used as monitor names in polybar. So like… this is the one with the full guest list πŸ’Œ
  • -w, --print-wmname β€” print the generated WM_NAME and exit.
  • -s, --stdout β€” output the data to stdout instead of drawing it to the X window. Terminal girlies rise 🌈
  • -p, --png=FILE β€” save a png snapshot to FILE after running for 3 seconds. Cute screenshot moment πŸŽ€

πŸ‘‘ AUTHORS πŸ‘‘

Polybar was created by Michael Carlberg and is currently maintained by Patrick Ziegler. Contributors can be listed on GitHub. Shoutout to the whole crew, fr fr 🫢


πŸ’€ REPORTING BUGS πŸ’€

Report issues on GitHub: <https://github.com/polybar/polybar>

Like… if something's broken, tell them, not me πŸ™ˆ


🌈 SEE ALSO 🌈


2016-2024, Michael Carlberg & contributors.


That's the whole page, bestie. You're officially polybar-literate. Slay. πŸ’…βœ¨

This was version 3.7.2, dated Sep 10, 2024 β€” and yes, that's the POLYBAR(1) manual, signed off with love πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from