From cd1aa57a0650d62f15182d0103e0971784d26e7e Mon Sep 17 00:00:00 2001 From: Bakkeby Date: Thu, 18 Aug 2022 17:30:18 +0200 Subject: [PATCH] Bump to 72fd327. st: use `void' to indicate an empty parameter list Ref. https://git.suckless.org/st/commit/72fd32736a612edec43596c14148322122a5544d.html --- README.md | 2 +- st.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 0c97e75..e53de1d 100644 --- 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 (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. +Similar to [dwm-flexipatch](https://github.com/bakkeby/dwm-flexipatch) this st 0.8.5 (72fd327, 2022-08-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. 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/st.c b/st.c index 0c557f0..d50c90e 100644 --- a/st.c +++ b/st.c @@ -1245,7 +1245,7 @@ ttyresize(int tw, int th) } void -ttyhangup() +ttyhangup(void) { /* Send SIGHUP to shell */ kill(pid, SIGHUP);