NapoleonDynamite/dwmblocks
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
No description
57 commits 1 branch 0 tags 132 KiB
C 95.4%
Makefile 4.6%
Find a file
Daniel Bylinka aaeebc4b36 Update status after forking and export with setenv 
Forking after updating the status can feel unresponsive depending on how
long it takes for the command to run.

Also link to the statuscmd page on suckless.org instead of the gist.
2020-05-18 00:52:18 +02:00
patches statuscmd programs forked 2020-05-04 15:27:46 -04:00
.gitignore Added code files, and Makefile. 2019-03-24 16:31:05 -06:00
config.h this should really be disabled until I fix it all 2020-05-04 17:26:37 -04:00
dwmblocks.c Update status after forking and export with setenv 2020-05-18 00:52:18 +02:00
LICENSE Initial commit 2019-03-24 16:19:32 -06:00
Makefile force clean 2020-04-08 11:06:01 -04:00
README.md Update status after forking and export with setenv 2020-05-18 00:52:18 +02:00

README.md

dwmblocks

Modular status bar for dwm written in c.

modifying blocks

The statusbar is made from text output from commandline programs. Blocks are added and removed by editing the blocks.h header file.

Luke's bulid

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 statusbar scripts.

signalling changes

For example, the audio module has the update signal 10 by default. Thus, running pkill -RTMIN+10 dwmblocks will update it.

clickable modules

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 $BLOCK_BUTTON variable.

For this feature to work, you need the appropriate patch in dwm as well. See here. Credit for those patches goes to Daniel Bylinka (daniel.bylinka@gmail.com).