-
Notifications
You must be signed in to change notification settings - Fork 29
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
Handle Content Types #13
Comments
Currently all non-target types are ignored, and it seems that throwing an error is the right thing to do. As for text/plain, we need to set multiple targets, which requires changing some APIs. I will try to fix it later. |
Thanks! Just to clarify, I personally don't care about non-text content types at all, since Alacritty won't ever have to handle them as far as I'm concerned. However, even then a quick error is obviously preferable over a long blocking timeout. |
@chrisduerr Can you try to see if this commit 0746c0e is valid? |
I can't reproduce any blocking issues anymore, so seems to be working great! Supporting explicitly set text content types would be the only remaining issue, however that's far less of a priority for me personally. So if that's gonna take a while and require API changes, a non-breaking fix release might be reasonable first. |
0.3.3 has been released! I will close this issue now and |
Using x11-clipboard through the clipboard-rust crate, it seems like content types lead to timeouts whenever trying to paste something.
This has been reported to Alacritty in alacritty/alacritty#2595.
I'd expect that when the content type is set to text/plain, everything should work the same way it does when no content type is set. Currently this operation times out.
If an image is loaded, I'd expect it to fail, however I'd expect it to fail instantly. Currently the operation also times out.
The text was updated successfully, but these errors were encountered: