st-flexipatch

My st-flexipatch configuration
git clone git://git.ethandl.dev/st-flexipatch
Log | Files | Refs | README | LICENSE

commit dc8abceecaa18c064c23b5296f74a3c55dce2cca
parent 4ccd248a50781e9ebb34c4156105c1db038c6aa1
Author: Bakkeby <bakkeby@gmail.com>
Date:   Sun, 10 Jul 2022 17:09:18 +0200

Makefile: add manual path for OpenBSD

ref. https://git.suckless.org/st/commit/baa9357e96d2478baa52a3301e70ac80a229b726.html

Diffstat:
MREADME.md | 2+-
Mconfig.mk | 1+
2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md @@ -1,4 +1,4 @@ -Similar to [dwm-flexipatch](https://github.com/bakkeby/dwm-flexipatch) this st 0.8.5 (ef05519, 2022-03-18) project has a different take on st 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. +Similar to [dwm-flexipatch](https://github.com/bakkeby/dwm-flexipatch) this st 0.8.5 (baa9357, 2022-05-01) project has a different take on st 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/st-flexipatch/blob/master/patches.def.h): ```c diff --git a/config.mk b/config.mk @@ -47,6 +47,7 @@ STLDFLAGS = $(LIBS) $(LDFLAGS) #LIBS = -L$(X11LIB) -lm -lX11 -lutil -lXft \ # `pkg-config --libs fontconfig` \ # `pkg-config --libs freetype2` +#MANPREFIX = ${PREFIX}/man # compiler and linker # CC = c99