Mercurial > vim
view src/testdir/test_termencoding.vim @ 16720:9c90cf08cfa8 v8.1.1362
patch 8.1.1362: code and data in tests can be hard to read
commit https://github.com/vim/vim/commit/c79745a82faeb5a6058e915ca49a4c69fa60ea01
Author: Bram Moolenaar <Bram@vim.org>
Date: Mon May 20 22:12:34 2019 +0200
patch 8.1.1362: code and data in tests can be hard to read
Problem: Code and data in tests can be hard to read.
Solution: Use the new heredoc style. (Yegappan Lakshmanan, closes https://github.com/vim/vim/issues/4400)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Mon, 20 May 2019 22:15:06 +0200 |
parents | 2dcaa860e3fc |
children | ba7727889385 |
line wrap: on
line source
" Test for setting 'encoding' to something else than the terminal uses, then " setting 'termencoding' to make it work. " This only works with "iconv". if !has('iconv') finish endif source screendump.vim if !CanRunVimInTerminal() finish endif " This Vim is running with 'encoding' "utf-8", the Vim in the terminal is " running with 'encoding' "euc-jp". We need to make sure the text is in the " right encoding, this is a bit tricky. func Test_termencoding_euc_jp() new call setline(1, 'E89: バッファ %ld の変更は保存されていません (! で変更を破棄)') write ++enc=euc-jp Xeuc_jp.txt quit call writefile([ \ 'set encoding=euc-jp', \ 'set termencoding=utf-8', \ 'scriptencoding utf-8', \ 'exe "normal aE83: バッファを作成できないので、他のを使用します...\<Esc>"', \ 'split Xeuc_jp.txt', \ ], 'XTest_tenc_euc_jp') let buf = RunVimInTerminal('-S XTest_tenc_euc_jp', {'rows': 10}) call VerifyScreenDump(buf, 'Test_tenc_euc_jp_01', {}) " clean up call StopVimInTerminal(buf) call delete('Xeuc_jp.txt') call delete('XTest_tenc_euc_jp') endfunc