csi: ‘CSI 13 ; 2 t’ reply is now (0,0)

Foot previously responded with window local coordinates.

But, XTerm responds with screen *absolute* coordinates. This isn’t
possible under Wayland, thus we now report (0,0) instead. Same as we
do for ‘CSI 13 ; 0 t’.
This commit is contained in:
Daniel Eklöf 2021-02-16 14:31:46 +01:00
parent 4ff07a0d18
commit 8658ab4bed
No known key found for this signature in database
GPG key ID: 5BBD4992C116573F
2 changed files with 4 additions and 3 deletions

View file

@ -65,6 +65,8 @@
before sending the new dimensions to the client application. The before sending the new dimensions to the client application. The
timing can be tweaked, or completely disabled, by setting timing can be tweaked, or completely disabled, by setting
`resize-delay-ms` (https://codeberg.org/dnkl/foot/issues/301). `resize-delay-ms` (https://codeberg.org/dnkl/foot/issues/301).
* `CSI 13 ; 2 t` now reports (0,0).
### Deprecated ### Deprecated
### Removed ### Removed

5
csi.c
View file

@ -1200,10 +1200,10 @@ csi_dispatch(struct terminal *term, uint8_t final)
case 13: { /* report window position */ case 13: { /* report window position */
/* We don't know our position - always report (0,0) */
int x = -1; int x = -1;
int y = -1; int y = -1;
/* We don't know our position - always report (0,0) */
switch (vt_param_get(term, 1, 0)) { switch (vt_param_get(term, 1, 0)) {
case 0: case 0:
/* window position */ /* window position */
@ -1212,8 +1212,7 @@ csi_dispatch(struct terminal *term, uint8_t final)
case 2: case 2:
/* text area position */ /* text area position */
x = term->margins.left; x = y = 0;
y = term->margins.top;
break; break;
default: default: