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
Byte overflow problem in SIXEL decoder #593
Comments
test patch: |
I wonder why and how SIXEL colour registers interfere with mintty's text colour handling. |
I think if we need to emulate old hardware faithfully, text color registers have to be shared with that of SIXEL. |
So if there is currently no dependence of SIXEL colors on text 256 colors (if I understood you correctly, haven't had time to test it yet, sorry), why was there this surprising interference of the 257th color with mintty default color indications? Just trying to understand. |
I was confused by "257th" color because a few internal attribute values above 256 are used for foreground etc by mintty. Unrelated, so forget my previous comments here. About the patch: Do we really need all the type definitions, int8, int16, int32, uint8... I'm asking because that doesn't compile with an older gcc version. |
…tty#593) uint8_t -> uchar uint32_t -> uint int32_t for palette -> colour
OK I use definitions of src/std.h and src/config.h in a664ed8. |
Thanks a lot. |
Thanks for merging! |
Released 2.6.2. |
I'm afraid I have to revert the latest patch from this issue, in order to resolve #740. |
revert reversion of Sixel colour registers patch (#593); fixed memory holes in error cases
Released 3.0.2. |
Forwarded from mattn/go-sixel#5.
The text was updated successfully, but these errors were encountered: