One could argue its a little more convenient. I personally like it because it won't disturb any window layout I had open already. Here's a thought: Rather than adding all the code to the terminal, a simple patch could be made which detects a certain escape and will pipe everything after that for X bytes into some image viewer. That could be another separate program. And we don't need to use sixel, we just push the raw farbfeld.
On 03/20/2017 02:40 PM, hiro wrote: > why would one want to view images in st, can't your shell start other > graphical programs for that? is st becoming a new kind of web browser > now? and why don't you open remote images using a remote file system > instead of fucking around with remote shells and then trying to > display them in a local terminal?! > > i mean even loonix can do this already. sshfs, qiv (or other proper > graphical application of your choice). you even have a window manager > in your same old project here, why not open some windows already? > > On 3/20/17, Laslo Hunhold <d...@frign.de> wrote: >> On Mon, 20 Mar 2017 02:57:20 +0300 >> Alexander Krotov <ilab...@gmail.com> wrote: >> >> Hey Alexander, >> >>> I have crafted a program to convert farbfeld images to sixels: >>> https://github.com/ilabdsf/ff2sixel >> this is very cool! Sixels are definitely an interesting concept to view >> images over an SSH-connection. >> >>> Too bad st does not have a patch to display sixels, so I am going >>> to use mlterm when I need to browse images. One simple way to >>> implement it in st is to cut out sixel images, convert them back >>> to farbfeld (with separate process) and pass result to lel. Not >>> going to do it now, just an idea. >> There were discussions on sixel support in st, and I think even some >> code written for it. Can anybody give a status update on that one? >> >> With best regards >> >> Laslo >> >> -- >> Laslo Hunhold <d...@frign.de> >> >>