Mercurial > vim
view src/testdir/test77a.in @ 12281:2738b0cc5f64 v8.0.1020
patch 8.0.1020: when a timer calls getchar(1) input is overwritten
commit https://github.com/vim/vim/commit/0f0f230012f5a9beb6876158a17b432534836c6f
Author: Bram Moolenaar <Bram@vim.org>
Date: Wed Aug 30 18:52:56 2017 +0200
patch 8.0.1020: when a timer calls getchar(1) input is overwritten
Problem: When a timer calls getchar(1) input is overwritten.
Solution: Increment tb_change_cnt in inchar(). (closes https://github.com/vim/vim/issues/1940)
| author | Christian Brabandt <cb@256bit.org> |
|---|---|
| date | Wed, 30 Aug 2017 19:00:05 +0200 |
| parents | 47a673b20e49 |
| children | e705ea6e855b |
line wrap: on
line source
Inserts 2 million lines with consecutive integers starting from 1 (essentially, the output of GNU's seq 1 2000000), writes them to Xtest and writes its cksum to test.out. We need 2 million lines to trigger a call to mf_hash_grow(). If it would mess up the lines the checksum would differ. cksum is part of POSIX and so should be available on most Unixes. If it isn't available then the test will be skipped. VMS does not have CKSUM but has a built in CHECKSUM - it should be used STARTTEST :so small.vim :if !has("vms") : e! test.ok : w! test.out : qa! :endif :set fileformat=unix undolevels=-1 ggdG :let i = 1 :while i <= 2000000 | call append(i, range(i, i + 99)) | let i += 100 | endwhile ggdd :w! Xtest. :r !@test77a.com Xtest. :s/\s/ /g :set fileformat& :.w! test.out :qa! ENDTEST