On Mon, 1 Aug 2016 17:13:14 +0200
Ton van den Heuvel wrote:
> Fallback fonts can already be configured through Fontconfig, why does
> st need separate functionality for this?
Because Fontconfig is a load of crap!
--
FRIGN
Modifies st to support user-defined fallback fonts specified in an
array. This change also resolves an issue where fallback fonts were used
in place of default fonts in an inconsistent manner which caused
identical sets of text to sometimes use different fonts.
---
config.def.h | 15 +---
On Mon, Aug 1, 2016 at 3:49 PM, FRIGN wrote:
>
> just update your patch and attach it to your response.
Fallback fonts can already be configured through Fontconfig, why does
st need separate functionality for this?
On Sun, 31 Jul 2016 19:08:34 -0700
Eric Pruitt wrote:
Hey Eric,
> I used tabs when editing st.c, but I just noticed I accidentally used
> spaces when I changed config.def.h. It's only one line, and I don't
> think it's worth creating another thread, but if aren't willing
Dear suckless folks,
just a small nit, that the imperative mood should be used in commit
message summaries/subjects.
> Convert "font" string to "fonts" array
It’s a little shorter and is also used by git’s default messages for
merging and reverting. [1][2]
In the end it’s not that
On Sun, Jul 31, 2016 at 08:26:36AM +0200, Jan Christoph Ebersbach wrote:
> Have you tried to increase patch's fuzz factor with the --fuzz option in
> order to achieve the same result?
I messed tried messing with the fuzzing factor, but I had some patches
apply in wrong place. I am not certain