1 # dwmblocks 2 3 Modular status bar for dwm written in c. 4 5 # Modifying blocks 6 7 The statusbar is made from text output from commandline programs. Blocks are 8 added and removed by editing the config.h file. 9 10 # Luke's build 11 12 I have dwmblocks read my preexisting scripts 13 [here in my dotfiles repo](https://github.com/LukeSmithxyz/voidrice/tree/master/.local/bin/statusbar). 14 So if you want my build out of the box, download those and put them in your 15 `$PATH`. I do this to avoid redundancy in LARBS, both i3 and dwm use the same 16 statusbar scripts. 17 18 # Signaling changes 19 20 Most statusbars constantly rerun every script every several seconds to update. 21 This is an option here, but a superior choice is giving your module a signal 22 that you can signal to it to update on a relevant event, rather than having it 23 rerun idly. 24 25 For example, the audio module has the update signal 10 by default. Thus, 26 running `pkill -RTMIN+10 dwmblocks` will update it. 27 28 You can also run `kill -44 $(pidof dwmblocks)` which will have the same effect, 29 but is faster. Just add 34 to your typical signal number. 30 31 My volume module *never* updates on its own, instead I have this command run 32 along side my volume shortcuts in dwm to only update it when relevant. 33 34 Note that if you signal an unexpected signal to dwmblocks, it will probably 35 crash. So if you disable a module, remember to also disable any cronjobs or 36 other scripts that might signal to that module. 37 38 # Clickable modules 39 40 Like i3blocks, this build allows you to build in additional actions into your 41 scripts in response to click events. See the above linked scripts for examples 42 of this using the `$BLOCK_BUTTON` variable. 43 44 For this feature to work, you need the appropriate patch in dwm as well. See 45 [here](https://dwm.suckless.org/patches/statuscmd/). 46 Credit for those patches goes to Daniel Bylinka (firstname.lastname@example.org).