aboutsummaryrefslogtreecommitdiff
path: root/test
diff options
context:
space:
mode:
authorzeertzjq <zeertzjq@outlook.com>2024-09-04 06:35:26 +0800
committerGitHub <noreply@github.com>2024-09-04 06:35:26 +0800
commit7b7c95dac97d6ea4f10855cc198dce650a796c20 (patch)
tree71141aa2610ecbcba5691fe69ec82c302cb30596 /test
parent45e76acaa053a077cab49b6606536d3f2646f033 (diff)
downloadrneovim-7b7c95dac97d6ea4f10855cc198dce650a796c20.tar.gz
rneovim-7b7c95dac97d6ea4f10855cc198dce650a796c20.tar.bz2
rneovim-7b7c95dac97d6ea4f10855cc198dce650a796c20.zip
vim-patch:9.1.0713: Newline causes E749 in Ex mode (#30254)
Problem: Newline causes E749 in Ex mode (after 9.1.0573). Solution: Don't execute empty command followed by a newline. closes: vim/vim#15614 https://github.com/vim/vim/commit/2432b4a75321a1a9ac0f9b326c7e46d38bdb71bb Cherry-pick code change from patch 8.2.3405.
Diffstat (limited to 'test')
-rw-r--r--test/old/testdir/test_ex_mode.vim16
1 files changed, 16 insertions, 0 deletions
diff --git a/test/old/testdir/test_ex_mode.vim b/test/old/testdir/test_ex_mode.vim
index 9f3ee2194e..32b01fef9e 100644
--- a/test/old/testdir/test_ex_mode.vim
+++ b/test/old/testdir/test_ex_mode.vim
@@ -316,4 +316,20 @@ func Test_global_insert_newline()
bwipe!
endfunc
+" An empty command followed by a newline shouldn't cause E749 in Ex mode.
+func Test_ex_empty_command_newline()
+ let g:var = 0
+ call feedkeys("gQexecute \"\\nlet g:var = 1\"\r", 'xt')
+ call assert_equal(1, g:var)
+ call feedkeys("gQexecute \" \\nlet g:var = 2\"\r", 'xt')
+ call assert_equal(2, g:var)
+ call feedkeys("gQexecute \"\\t \\nlet g:var = 3\"\r", 'xt')
+ call assert_equal(3, g:var)
+ call feedkeys("gQexecute \"\\\"?!\\nlet g:var = 4\"\r", 'xt')
+ call assert_equal(4, g:var)
+ call feedkeys("gQexecute \" \\\"?!\\nlet g:var = 5\"\r", 'xt')
+ call assert_equal(5, g:var)
+ unlet g:var
+endfunc
+
" vim: shiftwidth=2 sts=2 expandtab