new version not have binary file about timg

[hzeller]

I am considering building an app-image in the CI as this seems to be the most commonly single-binary type that should work on most platforms out of the box. I'll need to play github actions a bit to make it happen.

[hzeller]

The CI now builds an AppImage.

Here is such an output timg-1.5.0-x86_64.AppImage.zip - please try if it works for you.

The video decoding is excluded as it would increase the size of the AppImage at least 5x (and it is already 10MiB).
But at least such AppImage might help people get started to play with it before they decide to just regular install via their package manager or compile.

I'll soon make a patchlevel release 1.5.1, then I'll put such binary in that release.

[hzeller]

What terminal are you using ? For high resolution, the terminal needs to support either Sixel, iterm2, or Kitty protocol.

Not all of these can be auto-detected, so you might need to specifically add -ps , -pi, or -pk to the command line to choose the way it emits the image.

[hzeller]

The standard Alacritty can't do high resolution images.

However, there is another alacritty that understands Sixel: https://github.com/microo8/alacritty-sixel

[hzeller]

tmux filters out all image escape codes. There is a fork of tmux that can deal with it: https://github.com/csdvrx/sixel-tmux

[hzeller]

I've now implemented workarounds to show high-resolution images in Kitty for #95 (requires Kitty terminal).

[hzeller]

AppImage now part of the latest release v1.5.1