markus-bauer

Can you provide an example of how this would be integrated? I don't know how much you're familiar with ranger's codebase. Or how image previews work.

> By the way, why does ranger still support python 2.6+ the lower 3.X?... I've got some assumptions but don't wanna live by that. I'm not a ranger dev, so...

I think this issue already exists: https://github.com/ranger/ranger/issues/2361 If this is the same, then this might be fixed in the master branch (see the discussion there). Did you search for existing...

@remi6397: You could cache the sixel images. Here's an example, based on how the caching of previews in get_preview works. I did a quick test and it's definitely better than...

Don't know about that one. What does it do? This saves the sixel image on disk and loads it if it's available at the correct size.

I looked at it just now and `cached_function` returns the return value of the decorated function. You could rewrite the displayer to work with that, I think. The cache would...

Final note: This keeps one cached sixel image per image path + preview dimension. If you change the size, for example when opening in the pager, it will remake the...

Good job. It works much better than before and is obviously way better than my version. Questions: - Why does _CachedSixelImage store cached, and not just the memory mapped file?...

> It's not, we just hold on to the open fd as long as we need it. The actual contents are not stored in memory unless I made some stupid...

The new version has a mistake, you forgot to add path: ``` AttributeError: '_CacheableSixelImage' object has no attribute 'path' ``` About connecting with fsobject: It was just an idea. (But...