Mercurial > vim
view src/testdir/test_plus_arg_edit.vim @ 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 | 2dcaa860e3fc |
children | 2f4be7ca1b1b |
line wrap: on
line source
" Tests for complicated + argument to :edit command function Test_edit() call writefile(["foo|bar"], "Xfile1") call writefile(["foo/bar"], "Xfile2") edit +1|s/|/PIPE/|w Xfile1| e Xfile2|1 | s/\//SLASH/|w call assert_equal(["fooPIPEbar"], readfile("Xfile1")) call assert_equal(["fooSLASHbar"], readfile("Xfile2")) call delete('Xfile1') call delete('Xfile2') endfunction func Test_edit_bad() " Test loading a utf8 file with bad utf8 sequences. call writefile(["[\xff][\xc0][\xe2\x89\xf0][\xc2\xc2]"], "Xfile") new " Without ++bad=..., the default behavior is like ++bad=? e! ++enc=utf8 Xfile call assert_equal('[?][?][???][??]', getline(1)) e! ++enc=utf8 ++bad=_ Xfile call assert_equal('[_][_][___][__]', getline(1)) e! ++enc=utf8 ++bad=drop Xfile call assert_equal('[][][][]', getline(1)) e! ++enc=utf8 ++bad=keep Xfile call assert_equal("[\xff][\xc0][\xe2\x89\xf0][\xc2\xc2]", getline(1)) call assert_fails('e! ++enc=utf8 ++bad=foo Xfile', 'E474:') bw! call delete('Xfile') endfunc