-
Notifications
You must be signed in to change notification settings - Fork 127
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
Problems with st-sixel #32
Comments
Thank you for reminding me of this issue. The problem is that |
In the discussion of the patch, @charlesdaniels says,
Maybe Charles does indeed wish to implement a fix and just needs a nudge? |
I don't use When I was using it actively, I simply patched my copy of Perhaps |
Yet another active fork: LukeSmithxyz/st
|
I would like to note that my fork of If someone really wants to do this right, it would be best to start with a fresh copy of Sixel is not a terribly complicated format. I think that a C programmer with a good knowledge of xlib could do this right in a weekend or two. My xlib skills are not so good though, hence why I didn't do that myself. Good luck! |
Done. I understand you're not working with st any more, but do you think you could add just the small fix I suggested? Basically, instead of returning 6, return 12;4 to Send Device Attributes. I see that your repository is the upstream for five other repositories that use your sixel implementation. It'd be easiest to get this fixed in your repo than in each of those. Thanks. |
I'll see what I can do. It's been a long time since I looked the handling for escape codes, but this shouldn't be too hard. I should probably also update the README to indicate it's not active anymore while I'm at it. |
@bakkeby, could you look into adding this into |
I think I have fixed it, hope this resolves your troubles! |
Hi
I'm using st-sixel (https://github.com/galatolofederico/st-sixel) which lsix doesn't realise has sixel capabilities. I got lsix working on it by brute force (setting hassixel=yup) but I don't the clever (correct) way to do this.
Hope you're able to help
Ta
The text was updated successfully, but these errors were encountered: