rebase off of Luke's dwmblocks

1 files changed, 10 insertions, 8 deletions

diff --git a/README.md b/README.md
index b6a4685..aa0ee05 100644
--- a/README.md
+++ b/README.md
@@ -2,18 +2,22 @@
 
 Modular status bar for dwm written in c.
 
+# ZachIR's fork of Luke Smith's config of dwmblocks
+
+Hence, most of what you see below will be very familiar if you read Luke's
+README.
+
 # Modifying blocks
 
 The statusbar is made from text output from commandline programs.  Blocks are
 added and removed by editing the config.h file.
 
-# Luke's build
+# ZachIR's build
 
 I have dwmblocks read my preexisting scripts
-[here in my dotfiles repo](https://github.com/LukeSmithxyz/voidrice/tree/master/.local/bin/statusbar).
+[here in my scripts repo](https://gitlab.com/zachir/scripts).
 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.
+`$PATH`.
 
 # Signaling changes
 
@@ -22,7 +26,7 @@ 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,
+For example, the volume module has the update signal 10 by default.  Thus,
 running `pkill -RTMIN+10 dwmblocks` will update it.
 
 You can also run `kill -44 $(pidof dwmblocks)` which will have the same effect,
@@ -31,9 +35,7 @@ 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 if you signal an unexpected signal to dwmblocks, it will probably
-crash. So if you disable a module, remember to also disable any cronjobs or
-other scripts that might signal to that module.
+Note that all modules must have different signal numbers.
 
 # Clickable modules