Extend image backend support to ITerm2 Inline Images Protocol.

[o2sh]

As mentioned by @yoichi in #266, even though iterm2 seems to support SIXEL; it shows a broken output:

Apparently, iterm2 has its own rendering protocol which extends the xterm protocol with a set of proprietary escape sequences. This xterm protocol must be the SIXEL protocol - Implemented by @CephalonRho - or smth close to it.

[mborejdo]

Looking forward to this. https://github.com/wez/wezterm is an awesome terminal-emulator with great Windows support. It also supports the iTerm2 inline image protocol and it would be great to have some windows love :-)

[o2sh]

From what I understood, @yoichi opened an issue addressing this problem which was fixed in this commit

Unfortunately, I don't have a machine running macOS so I can't test it 😞

[mborejdo]

Hey @o2sh. thanks for your reply. I am not sure I understand. Does this mean the iterm2 inline image support (which works also on windows on wezterm) will not be added, once the sixel-issue is resolved?

[o2sh]

@mborejdo, wezterm also supports Sixel

However, this won't work on Windows.

[mborejdo]

hey @o2sh . Yes, thats really unfortunate. Thats why I was hoping to have the iterm2-inline-image working on windows as this works as expected (almost)
Also unfortunately onefetch's --ascii does not help here, as the commandline is limited in length. Would it be possible to provide something like --ascii-file or the like so I could pass the base64 encoded inline-image to onefetch to be displayed instead of the default?

[o2sh]

Also unfortunately onefetch's --ascii does not help here, as the commandline is limited in length.

Try this onefetch ––ascii-input "$(cat image_base64.txt)"

---

Once @yoichi’s PR is merged, we’ll still have to tweak it a bit to have it work on windows.