forked from aniani/vim
patch 9.0.1598: screenchar() and others are wrong with DBCS 'encoding'
Problem: screenchar(), screenchars() and screenstring() do not work
properly when 'encoding' is set to a double-byte encoding.
Solution: Fix the way the bytes of the characters are obtained.
(issue #12469)
This commit is contained in:
@@ -135,6 +135,19 @@ func Test_screenchar_utf8()
|
||||
call assert_equal("B", screenstring(1, 2))
|
||||
call assert_equal("C\u0308", screenstring(1, 3))
|
||||
|
||||
" 1-cell, with 6 composing characters
|
||||
set maxcombine=6
|
||||
call setline(1, ["ABC" .. repeat("\u0308", 6)])
|
||||
redraw
|
||||
call assert_equal([0x0041], screenchars(1, 1))
|
||||
call assert_equal([0x0042], 1->screenchars(2))
|
||||
" This should not use uninitialized memory
|
||||
call assert_equal([0x0043] + repeat([0x0308], 6), screenchars(1, 3))
|
||||
call assert_equal("A", screenstring(1, 1))
|
||||
call assert_equal("B", screenstring(1, 2))
|
||||
call assert_equal("C" .. repeat("\u0308", 6), screenstring(1, 3))
|
||||
set maxcombine&
|
||||
|
||||
" 2-cells, with composing characters
|
||||
let text = "\u3042\u3044\u3046\u3099"
|
||||
call setline(1, text)
|
||||
|
||||
Reference in New Issue
Block a user