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
Erratic behavior of chafa -f iterm image.jpg
on Windows
#194
Comments
Duplicate of #186 |
Thanks for filing the issue, @ykhan21. I think @AnonymouX47 is right - the short version is that Chafa is a native Windows app, and the Wezterm binary is a Cygwin app. These are different platforms that don't play well together. We need to add Cygwin builds (or alternatively, other apps should be made native). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Setup:
On Windows:
scoop bucket add main
, runscoop bucket add extras
, and finally runscoop install git wezterm chafa
.scoop install git
. To do this, create a ~/.wezterm.lua file with these contents:See https://wezfurlong.org/wezterm/config/files.html for more details.
Problem:
On Wezterm,
chafa -f iterm image.jpg
sometimes outputs extra space at the end like so:Notice that the shell prompt starts at the bottom right of the image above.
On mintty (the terminal called Git Bash that is installed when you install Git for Windows is mintty), most of the time,
chafa -f iterm image.jpg
does not display an image and instead results in a large amount of whitespace, almost as if it were displaying an empty image. Very rarely it displays a distorted half of the image. Theshowimg
script found here works correctly to show images in mintty (Git Bash) in the iterm format.The text was updated successfully, but these errors were encountered: