jasper
/
dwmblocks
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
40 Commits
1 Branch
0 Tags
77 KiB
C 94%
Makefile 6%
 
 
jasper/latest
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '5dcb2a0d84'
${ noResults }
Go to file
aidan 5dcb2a0d84 fixed signal handling on OpenBSD by using SIGUSR1 instead of SIGRTMIN. 
This should not affect other platforms at all.
 		5 years ago
.gitignore added blocks.def.h to act as default blocks file so that changes made in 5 years ago
LICENSE Switched to ISC license 5 years ago
Makefile added blocks.def.h to act as default blocks file so that changes made in 5 years ago
README.md Update README.md 5 years ago
blocks.def.h added blocks.def.h to act as default blocks file so that changes made in 5 years ago
dwmblocks.c fixed signal handling on OpenBSD by using SIGUSR1 instead of SIGRTMIN. 5 years ago

README.md

dwmblocks

Modular status bar for dwm written in c.

usage

To use dwmblocks first run 'make' and then install it with 'sudo make install'. After that you can put dwmblocks in your xinitrc or other startup script to have it start with dwm.

modifying blocks

The statusbar is made from text output from commandline programs. Blocks are added and removed by editing the blocks.h header file. By default the blocks.h header file is created the first time you run make which copies the default config from blocks.def.h. This is so you can edit your status bar commands and they will not get overwritten in a future update.

patches

Here are some patches to dwmblocks that add features that I either don't want to merge in, or that require a dwm patch to work. I do not maintain these but I will take pull requests to update them.
dwmblocks-statuscmd-signal.diff