Signed-off-by: Marcin Woźniak <firstname.lastname@example.org>
|1 year ago|
|patches||1 year ago|
|.gitignore||1 year ago|
|FUNDING.yml||1 year ago|
|LICENSE||1 year ago|
|Makefile||1 year ago|
|README.md||1 year ago|
|config.h||1 year ago|
|dwmblocks.c||1 year ago|
THANK YOU LUKE FOR YOUR HARD WORK
Modular status bar for dwm written in c.
The statusbar is made from text output from commandline programs. Blocks are added and removed by editing the config.h file.
I have dwmblocks read my preexisting scripts
here in my dotfiles repo.
So if you want my build out of the box, download those and put them in your
$PATH. I do this to avoid redundancy in LARBS, both i3 and dwm use the same
Most statusbars constantly rerun every script every several seconds to update. This is an option here, but a superior choice is giving your module a signal that you can signal to it to update on a relevant event, rather than having it rerun idly.
For example, the audio module has the update signal 10 by default. Thus,
pkill -RTMIN+10 dwmblocks will update it.
You can also run
kill -44 $(pidof dwmblocks) which will have the same effect,
but is faster. Just add 34 to your typical signal number.
My volume module never updates on its own, instead I have this command run along side my volume shortcuts in dwm to only update it when relevant.
Note that all modules must have different signal numbers.
Like i3blocks, this build allows you to build in additional actions into your
scripts in response to click events. See the above linked scripts for examples
of this using the