Results 103 comments of Hayaki Saito

cannot reproduce on `master` (`v1.8.7`); also not reproducible after checking out `v1.8.6`.

`at src/quant.c:871:9` on `master` (`v1.8.6` and `v1.8.7`) I only see the harmless ``` if (c < 0) { ``` so could you confirm which branch you tested If it’s `develop`,...

@eabase As mentioned in the mintty issue, this problem is likely a problem with the ConPTY or Console API layer. After trying various workarounds, I found that it works fine...

This issue is reproducible on my Windows 11 environment as well. Incidentally, it seems that builds which depend on a cygwin1.dll built under Cygwin do not exhibit this issue. Interesting.

Findings: - The issue also occurs over SSH (≈ not a terminal-specific problem). - It does not occur with Cygwin builds (binaries linked against cygwin1.dll / msys-2.0.dll). - It does...

Thanks for looking into this. I can reproduce the same behavior with Python installed via pacman in a MinGW/UCRT environment, so I don’t think this is a libsixel-specific issue. My...

I agree the current build script is quite large and unwieldy, but it doesn’t seem directly related to this issue. If there’s demand, I’m open to adding support for building...

Using the code that @elieux shared, I put together a workaround. For reasons I don’t fully understand, you need to pass the `-mwindows` option to the linker. https://github.com/saitoha/libsixel/commit/6569ed6ca00024788d8761d052487357a9b88638 On my...

If we build with `make LDFLAGS=-Wl,-static`, it also removes the dependency on `libwinpthread-1.dll`, so we should be able to ship a single, self-contained binary.