dwmbar is a very simple status bar written for dwm.
This project is no longer actively maintained. You will likely not receive support from the devs if something's not right. If you are somebody who is interested in taking over this project, please contact me (thytom) and we can discuss adding you as a contributor. You are also more than welcome to fork the project if you wish to make improvements on your own.
While some modules will work without these dependencies, we recommend grabbing the ones you want for specific modules.
Highly Recommended:
Optional (By module):
See module prerequisites.
There is an AUR package for dwmbar, which can be installed with your favourite aur helper, or manually.
Please see the archwiki page for how to manually install AUR packages.
$ git clone https://github.com/thytom/dwmbar
$ cd dwmbar
$ sudo ./install.sh
dwmbar works by setting the root window name, which dwm displays. It does this by calling the dwmbarrc file in your .config/dwmbar folder.
Add the line dwmbar &
to your .xinitrc file to run on startup. You can also
run dwmbar
in terminal for testing purposes.
Most non-modular configuration is done in ~/.config/dwmbar/dwmbarrc
, a bash
script that calls scripts in turn, caching their output and then constructing
the bar from that.
To add a module to the bar, simply include its name in the MODULES variable:
MODULES="mpd volumebar wifi battery"
Modules are displayed left-to-right in the order they are written in MODULES
.
By default, they are delimited by the SEPARATOR
variable, which you can
change.
We also offer a PADDING
variable, which contains a string you can include at
the start of your bar, on the very right. This can either be padding spaces, to
move the bar away from the right edge, or even text. By default, we set
PADDING
to $USER@$HOSTNAME
. Feel free to change this.
Default modules are located within /usr/share/dwmbar/modules
, and custom
modules can be placed in ~/.config/dwmbar/modules/custom
. If a default module
exists with the same name as a custom module, then the custom module will take
precedence.
Default modules will possibly be overwritten during updates, so if you want to modify them be sure to make a copy in the custom folder, which will not be touched, and edit it there.
Modules can be written in any language, so long as they are executable and print their output to stdout.
Currently available default modules are:
See Module Dependencies