diff options
| author | Daniel Eklöf <daniel@ekloef.se> | 2021-03-06 14:03:47 +0000 |
|---|---|---|
| committer | Daniel Eklöf <daniel@ekloef.se> | 2021-03-06 14:03:47 +0000 |
| commit | c95c6639899a3fd50256352eb552b4f302fd6d6b (patch) | |
| tree | 16839c77581eb2dac60165b9083209fb7e1868c1 /input.c | |
| parent | url-mode: fix auto-detection of URLs in the top corner of the viewport (diff) | |
sixel: size provided by DECGRA does *not* limit the sixel size
Foot has, up until now, used a fixed image size when the application
used DECGRA (Raster Attributes) to “configure” the image size.
This was based on a misunderstanding, that this was how you emitted
sixels where the height was *not* a multiple of 6.
This isn’t the case. The VT340 documentation is actually pretty clear
about this:
Ph and Pv do not limit the size of the image defined by the sixel
data. However, Ph and Pv let you omit background sixel data from the
image definition and still have a color background. They also
provide a concise way for the application or terminal to encode the
size of an image.
This is also how XTerm behaves. Test image:
\EPq
"1;1;1;1
#0;2;0;0;0#1;2;100;100;0#2;2;0;100;0
#1~~@@vv@@~~@@~~$
#2??}}GG}}??}}??-
#1!14@
\E\
This uses DECGRA to set the image size to 1x1. The sixel however
is *not* clipped to 1x1, but is resized to 14x12
Diffstat (limited to 'input.c')
0 files changed, 0 insertions, 0 deletions
