summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorbakkeby <[email protected]>2020-04-02 08:43:00 +0200
committerbakkeby <[email protected]>2020-04-02 12:43:48 +0200
commit32030e4b2cfcf544eae37820a8aa6a0c5a099695 (patch)
tree7b00d05ec70f6cc333ec03d215e3a4a5b53579d7
parentd9337195f3800fa422b27b0398c2542e635eca8d (diff)
downloaddwm-flexipatch-32030e4b2cfcf544eae37820a8aa6a0c5a099695.tar.gz
dwm-flexipatch-32030e4b2cfcf544eae37820a8aa6a0c5a099695.zip
Correcting link to patches.h following move to patches.def.h
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index e98bf26..94b5a42 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,6 @@
This dwm 6.2 side project has a different take on dwm patching. It uses preprocessor directives to decide whether or not to include a patch during build time. Essentially this means that this build, for better or worse, contains both the patched _and_ the original code. The aim being that you can select which patches to include and the build will contain that code and nothing more.
-For example to include the `alpha` patch then you would only need to flip this setting from 0 to 1 in [patches.h](https://github.com/bakkeby/dwm-flexipatch/blob/master/patches.h):
+For example to include the `alpha` patch then you would only need to flip this setting from 0 to 1 in [patches.h](https://github.com/bakkeby/dwm-flexipatch/blob/master/patches.def.h):
```c
#define ALPHA_PATCH 1
```