M. Zhou

Maybe we can setup a CI for windows build and see how far it goes

according to the buildlog, the build failed because the linker cannot find `_spawnv` ``` bin/sh ../libtool --tag=CC --mode=link gcc -Wall -Wextra -Wmissing-prototypes -ffast-math -DLODEPNG_NO_COMPILE_ENCODER -DLODEPNG_NO_COMPILE_DISK -DLODEPNG_NO_COMPILE_CPP -DLODEPNG_NO_COMPILE_CRC -I/mingw64/include/glib-2.0 -I/mingw64/lib/glib-2.0/include -mms-bitfields...

awesome! I'd request for vim-style keybinding for the interactive mode. `up, down, left, right` are also mapped to `h, j, k, l` zoom in / out (`+/-`) are also mapped...

That would be interesting. I used to call the `chafa` binary program from `os.system` in some of my python programs.

Now the goal of this issue turned into 1. find the optimal set of glyphs 2. documentation 3. autotools: add option to enable this feature

Let's move forward a bit: update the font generator and really ship a (basically working) font file?

Sounds good to me. > maybe we should be using a more compact format instead of JSON. Any suggestion? I think JSON is just the format of best compatibility, even...

Cool! I like this idea.

Nice. Now I think the C code generation part can be safely removed from `fontgen`. Will submit a PR to overhaul fontgen when I got enough time to work on...

I was always ignoring that error message but nothing went wrong actually.