st-flexipatch

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

commit 93aac7e1a3813e6335ca961586f45c5256d6e728
parent 01e341edd550ca05b8da93d75351a6bf9e10f0ca
Author: bakkeby <bakkeby@gmail.com>
Date:   Thu, 25 Jun 2020 12:43:25 +0200

bump version to 0.8.4

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

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.3 (249ef9, 2020-06-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. +Similar to [dwm-flexipatch](https://github.com/bakkeby/dwm-flexipatch) this st 0.8.4 (367803, 2020-06-19) 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 @@ -15,6 +15,8 @@ Refer to [https://st.suckless.org/](https://st.suckless.org/) for details on the ### Changelog: +2020-06-25 - Upgrade to 0.8.4 (367803, 2020-06-19) + 2020-06-14 - Added w3m patch 2020-06-10 - Upgrade to 249ef9, 2020-06-01 diff --git a/config.mk b/config.mk @@ -1,5 +1,5 @@ # st version -VERSION = 0.8.3 +VERSION = 0.8.4 # Customize below to fit your system