Image support

[w3bb]

What do you want

Ability to display images using Ueberzug, w3m, or some other solution.

Why

It would be way less of a pain to have to open images by hand.

Implementation hints

Perhaps a solution would be to allow users to add some sort of image handling script like Ranger does?

[w3bb]

Now that I think about it this could be done with the scripting interface. Have an event for images appearing, and an event for shifting the image up.

[Bios-Marcel]

Could you elaborate on that? What would the API look like?

[w3bb]

The idea I had was for Cordless to call a script with parameters for the position of the image. However I didn't know the scripting interface existed and I'm not to familiar with it.

[Bios-Marcel]

yeah, dunno bout that. The scripting engine is a confined JS engine without access to the operating system that can only use specified APIs to interact with cordless.

[w3bb]

Oh I figured it was shell script.

[Bios-Marcel]

I didn't want this to be something that people download scripts for that just bust their whole fucking system :)

[w3bb]

It wouldn't bust their system since if they use a TUI they probably know how to be savvy, but maybe native support for w3m/ueberzug might work better?

[ChillerDragon]

maybe use this: https://github.com/qeesung/image2ascii#library-usage

[Bios-Marcel]

@ChillerDragon That might actually be cool. I already considered that

[Bios-Marcel]

In all honestly, it doesn't make sense unless your images are always tiny. Because even a font-size of smth like 10px, which is already small, obviously takes more space than a pixel. Instead, more focus should be put on easily allowing to open links (images) outside of cordless.

Regarding ueberzug or anything. I think this kind of defies the laws of the terminal. It isn't crossplatform and won't even run in all linux terminals. Therefore I am not going introduce the complexity for such a tiny target audience.

Therefore, smth like #241 would be more interesting.