From 415fa6ccad53693a7ee2c950ca6c58c594b12ffe Mon Sep 17 00:00:00 2001 From: bakkeby Date: Thu, 2 Apr 2020 06:43:00 +0200 Subject: [PATCH] Correcting link to patches.h following move to patches.def.h --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 518e243..2edaeb4 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ Similar to [dwm-flexipatch](https://github.com/bakkeby/dwm-flexipatch) this dmenu 4.9 (750b30, 2019-03-03) project has a different take on 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 `border` patch then you would only need to flip this setting from 0 to 1 in [patches.h](https://github.com/bakkeby/dmenu-flexipatch/blob/master/patches.h): +For example to include the `border` patch then you would only need to flip this setting from 0 to 1 in [patches.h](https://github.com/bakkeby/dmenu-flexipatch/blob/master/patches.def.h): ```c #define BORDER_PATCH 1 ```