view src/libvterm/t/16state_resize.test @ 16764:ef00b6bc186b v8.1.1384

patch 8.1.1384: using "int" for alloc() often results in compiler warnings commit https://github.com/vim/vim/commit/964b3746b9c81e65887e2ac9a335f181db2bb592 Author: Bram Moolenaar <Bram@vim.org> Date: Fri May 24 18:54:09 2019 +0200 patch 8.1.1384: using "int" for alloc() often results in compiler warnings Problem: Using "int" for alloc() often results in compiler warnings. Solution: Use "size_t" and remove type casts. Remove alloc_check(), Vim only works with 32 bit ints anyway.
author Bram Moolenaar <Bram@vim.org>
date Fri, 24 May 2019 19:00:07 +0200
parents b8299e742f41
children
line wrap: on
line source

INIT
WANTSTATE g

!Placement
RESET
PUSH "AB\e[79GCDE"
  putglyph 0x41 1 0,0
  putglyph 0x42 1 0,1
  putglyph 0x43 1 0,78
  putglyph 0x44 1 0,79
  putglyph 0x45 1 1,0

!Resize
RESET
RESIZE 27,85
PUSH "AB\e[79GCDE"
  putglyph 0x41 1 0,0
  putglyph 0x42 1 0,1
  putglyph 0x43 1 0,78
  putglyph 0x44 1 0,79
  putglyph 0x45 1 0,80
  ?cursor = 0,81

!Resize without reset
RESIZE 28,90
  ?cursor = 0,81
PUSH "FGHI"
  putglyph 0x46 1 0,81
  putglyph 0x47 1 0,82
  putglyph 0x48 1 0,83
  putglyph 0x49 1 0,84
  ?cursor = 0,85

!Resize shrink moves cursor
RESIZE 25,80
  ?cursor = 0,79

!Resize grow doesn't cancel phantom
RESET
PUSH "\e[79GAB"
  putglyph 0x41 1 0,78
  putglyph 0x42 1 0,79
  ?cursor = 0,79
RESIZE 30,100
  ?cursor = 0,80
PUSH "C"
  putglyph 0x43 1 0,80
  ?cursor = 0,81