866c88c1d3
Remove EVENT_SCROLL_{UP_DOWN} since it is not being used.
Change EVENT_PREFIX to include dash and event names to be just the name without
the prefix, for simplified parsing. Use check_send_cmd function to parse the
cmd, using the event name as the IPC command name, and the section after the
event name to be the argument. The format of a cmd would be "dwm-<event
name>-<arg>", so the cmd can easily be translated into an IPC command.
Call member functions for all dwmipc events for better organization and to avoid
cluttering the constructor. The dwmipc event functions are now just assigned to
a lambda that calls a member function.
Add update_tag_labels function for updating the tag labels based on their state
since this code is repetetive.
Add update_title_labels function since that code is also somewhat repetetive.
Move reconnect code to reconnect_dwm for better organization.
Use pointers to m_monitors array elements instead of holding onto indices, since
most of the time, a member of the Monitor element will need to be accessed.
These variables should always hold a valid address starting in the constructor,
so checks for nullptr should not be necessary. A monitor will always be active
and the bar will always be mapped onto a monitor.
Add some comments where needed.
Reorganize the constructor into a more logical format
Only subscribe to events if their labels are included in the default format.
Follow clang-tidy warnings and use trailing return types.
Move m_ipc->get_monitors to update_monitor_ref since in most cases where the
monitor references would need to be updated using geometry, m_ipc->get_monitors
would need to be called.
|
||
|---|---|---|
| .github | ||
| cmake | ||
| common | ||
| contrib | ||
| doc | ||
| include | ||
| lib | ||
| src | ||
| tests | ||
| .clang-format | ||
| .clang-tidy | ||
| .codecov.yml | ||
| .editorconfig | ||
| .gitignore | ||
| .gitmodules | ||
| .valgrind-suppressions | ||
| .ycm_extra_conf.py | ||
| banner.png | ||
| build.sh | ||
| CHANGELOG.md | ||
| CMakeLists.txt | ||
| config.cmake | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.md | ||
| SUPPORT.md | ||
| version.txt | ||
A fast and easy-to-use tool for creating status bars.
Polybar aims to help users build beautiful and highly customizable status bars for their desktop environment, without the need of having a black belt in shell scripting. Here are a few screenshots showing you what it can look like:
You can find polybar configs for these example images (and other configs) here.
Table of Contents
Introduction
The main purpose of Polybar is to help users create awesome status bars. It has built-in functionality to display information about the most commonly used services. Some of the services included so far:
- Systray icons
- Window title
- Playback controls and status display for MPD using libmpdclient
- ALSA and PulseAudio volume controls
- Workspace and desktop panel for bspwm and i3
- Workspace module for EWMH compliant window managers
- Keyboard layout and indicator status
- CPU and memory load indicator
- Battery display
- Network connection details
- Backlight level
- Date and time label
- Time-based shell script execution
- Command output tailing
- User-defined menu tree
- Inter-process messaging
- And more...
See the wiki for more details.
Getting Help
If you find yourself stuck, have a look at our Support page for resources where you can find help.
Contributing
Read our contributing guidelines for how to get started with contributing to polybar.
Getting started
Polybar was already packaged for the distros listed below. If you can't find your distro here, you will have to build from source.
If you are using Debian (unstable or testing), you can install polybar using sudo apt install polybar.
If you are using Debian (buster/stable), you need to enable backports and then install using sudo apt -t buster-backports install polybar.
If you are using Arch Linux, you can install the AUR package polybar-git to get the latest version, or polybar for the latest stable release.
If you are using Void Linux, you can install polybar using xbps-install -S polybar.
If you are using NixOS, polybar is available in both the stable and unstable channels and can be installed with the command nix-env -iA nixos.polybar.
If you are using Slackware, polybar is available from the SlackBuilds repository.
If you are using Source Mage GNU/Linux, polybar spell is available in test grimoire and can be installed via cast polybar.
If you are using openSUSE, polybar is available from OBS repository. Package is available for openSUSE Leap 15.1, openSUSE Leap 15.2 and Tumbleweed.
If you are using FreeBSD, polybar can be installed using pkg install polybar. Make sure you are using the latest package branch.
If you are using Gentoo, both release and git-master versions are available in the main repository.
If you are using Fedora, you can install polybar using sudo dnf install polybar.
Installation
The compiling page on the wiki describes all steps necessary to build and install polybar.
Configuration
Details on how to setup and configure the bar and each module have been moved to the wiki.
Install the example configuration
Run the following inside the build directory:
$ make userconfig
Or you can copy the example config from /usr/share/doc/polybar/config or /usr/local/share/doc/polybar/config (depending on your install parameters)
Launch the example bar
$ polybar example
Running
See the wiki for details on how to run polybar.
Community
Want to get in touch?
- Join our Gitter room at gitter.im/polybar/polybar
- We have our own subreddit at r/polybar.
- Chat with us in the
#polybarIRC channel on thechat.freenode.netserver.
Contributors
Owner
- Michael Carlberg @jaagr
Maintainers
- @NBonaparte
- Chase Geigle @skystrife
- Patrick Ziegler @patrick96
Logo Design by
All Contributors
License
Polybar is licensed under the MIT license. See LICENSE for more information.