-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new version not have binary file #103
Comments
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. |
This is a preparation to run this script in the CI to allow to build AppImage artifacts. Issues #103
Build a timg AppImage with reduced dependencies (e.g. no video) to provide enough useful application for people to consider building and installing it fully. Issues: #103
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). I'll soon make a patchlevel release 1.5.1, then I'll put such binary in that release. |
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 |
The standard Alacritty can't do high resolution images. However, there is another alacritty that understands Sixel: https://github.com/microo8/alacritty-sixel |
tmux filters out all image escape codes. There is a fork of tmux that can deal with it: https://github.com/csdvrx/sixel-tmux |
I've now implemented workarounds to show high-resolution images in Kitty for #95 (requires Kitty terminal). |
AppImage now part of the latest release v1.5.1 |
No description provided.
The text was updated successfully, but these errors were encountered: