POLYBAR-MSG(1)
π NAME π
polybar-msg β the little messenger bestie that sends IPC messages to polybar, no cap π«Ά
okay so real quick: this is from the Polybar User Manual, and it's literally the glow-up you needed if you've ever wanted to talk to your bar like it's your group chat β¨
πΈ SYNOPSIS πΈ
polybar-msg [OPTIONS] action action-string
polybar-msg [OPTIONS] action module action [data]
polybar-msg [OPTIONS] cmd command
three whole ways to slide into polybar's DMs, pick your fighter π
π¦ DESCRIPTION π¦
So polybar lets the outside world control it β iconic behaviour honestly β through actions and commands. Here's the tea: actions are the ones that control individual modules, and commands control the bar itself. different tax brackets, y'know? π
The full IPC documentation is linked at the end of this document, go read it if you're nosy (affectionate). π
Which actions you actually get depends on the target module β so like, it's giving "results may vary" but in a cute way. For actions, the payload is either a single action string, or the module name, the action name, and the optional data string, all specified separately. two formats, both slay π
And for polybar-msg to be able to send a message to a running polybar process, two things gotta be true:
- the bar must have IPC enabled, and
- both
polybar-msgandpolybarmust run under the same user.
that's the vibe check. no shortcuts, sorry bestie π
β¨ OPTIONS β¨
-h,--helpβ display help text and exit π the classic "wait what does this do again" button-pPID β send the message only to the polybar process running under the given process ID. If you don't specify it, the message gets sent to all running polybar processes. so like,-pis the "no, this one" of flags π«Ά
π EXAMPLES π
polybar-msg cmd quit
Terminate all running polybar instances. bye bestie π literally all of them, no survivors, it's giving closing time π
polybar-msg action mymodule module_hide
polybar-msg action "#mymodule.module_hide"
Both of these hide the module named mymodule. The first variant specifies the module and action names separately, the second uses an action string. same energy, different outfit π
the way that both work is honestly so convenient
π AUTHORS π
Polybar was created by Michael Carlberg and is currently maintained by Patrick Ziegler. Contributors can be listed on GitHub β the whole squad, fr fr π
π REPORTING BUGS π
Found a bug? Report issues on GitHub <https://github.com/polybar/polybar> β don't suffer in silence, bestie, that's what the issue tracker is for ππ
π₯ SEE ALSO π₯
polybar(1),polybar(5)- IPC documentation: <https://polybar.rtfd.org/en/stable/user/ipc.html>
go click the IPC docs, iykyk π
β COPYRIGHT β
2016-2024, Michael Carlberg & contributors
okay that's the whole page, you ate that ngl π this was polybar-msg, version 3.7.2, dated Sep 10, 2024 β mwah, go send some messages to your bar, she's waiting ππΈπ¦
π¦ where this page comes from
- opensuse-leap 16.0: polybar 3.7.2-bp160.1.7 Β· MIT
- opensuse-leap 16.0: polybar 3.7.2-bp160.1.7 Β· MIT
- opensuse-leap 16.0: polybar 3.7.2-bp160.1.7 Β· MIT
- opensuse-leap 16.0: polybar 3.7.2-bp160.1.7 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms