Skip to content
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

Support alternative to writing directly to stdin #11

Open
bogzbonny opened this issue Apr 5, 2023 · 2 comments
Open

Support alternative to writing directly to stdin #11

bogzbonny opened this issue Apr 5, 2023 · 2 comments

Comments

@bogzbonny
Copy link

As much as I'd like to use pic as a library I've been unable to as pic within my CUI as it writes directly to stdin instead of allowing the caller of the library to decide how/when/where to write the graphic-escape-codes

For instance in my program I have a buffer which I flush once in a while which I write to ahead of time. If pic, under some feature flag, returned the string that it would normally be writing to stdin and which would allowed the caller of the library to process it I'd be able to successfully integrate it into my program.

Just an idea. I've ended up reimplemented a lot of the kitty image protocol for my own usage, would be a cool feature I reckon!

@emsquid
Copy link
Owner

emsquid commented Apr 5, 2023

Actually this is a good idea but it wouldn't work for all the protocols sadly, I can't do that with sixels as far as I know (unless I find another method, I will try to see).
I will think about it and find a cool way of implementing that!

@emsquid
Copy link
Owner

emsquid commented Apr 5, 2023

From my little research I should be able to get that working even for sixel, I'll be working on that soon!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants