You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The graphics protocol allows for a response suppression by setting the q key: q=1
In a multi-chunk transmission, this seems to require to set the q key for every chunk, while the documentation on chunk continuation escape sequences says that only the m key has to be set in subsequent chunks.
To Reproduce
Steps to reproduce the behavior:
# sending a two-pixel image in two chunks and suppressing the response using q=1echo -e "\e_Ga=T,i=42,q=1,s=2,v=1,f=24,m=1;////\e\\\\\e_Gm=0;////\e\\"
^[_Gi=42;OK^[\
What we see is the response of setting the image id even though we requested to have it suppressed with q=1
It works, if we repeat the q=1 key in the second chunk:
Refinement: it seems that only the last chunk decides what is happening. Here, we don't have the q=1 set in the first chunk, and only in the last chunk, which suppresses the OK-response:
Describe the bug
The graphics protocol allows for a response suppression by setting the q key:
q=1
In a multi-chunk transmission, this seems to require to set the
q
key for every chunk, while the documentation on chunk continuation escape sequences says that only them
key has to be set in subsequent chunks.To Reproduce
Steps to reproduce the behavior:
What we see is the response of setting the image id even though we requested to have it suppressed with
q=1
It works, if we repeat the
q=1
key in the second chunk:Expected behavior
Expected is that the
q
key does not have to be repeated in subsequent chunks like all the other key=value pairs.Environment details
Running on Linux, X11, compiled from head ( 958ccad )
The text was updated successfully, but these errors were encountered: