summaryrefslogtreecommitdiffstatshomepage
path: root/runtime/lua/_vim9script.lua
diff options
context:
space:
mode:
authorzeertzjq <zeertzjq@outlook.com>2025-04-21 16:56:05 +0800
committerGitHub <noreply@github.com>2025-04-21 08:56:05 +0000
commit351613bc1fce84acc368d944a635e7b696182c84 (patch)
treeae6d817017bdbd5fa5b7b6458aca0630c87ac017 /runtime/lua/_vim9script.lua
parent4b02d1f6f6e2ce866b6a9ec030c6a14609786e77 (diff)
vim-patch:187df69: runtime(doc): cross-link :| meaning :p and explain E749 (#33559)
E749 is given when :print (with any range) is issued on an empty buffer, like the one you get with :new or :enew. Furthermore, due to Vi compatibility :| is a synonym. As a result, mappings intended to include a <bar> separator (esp. in the case of boolean or "||") between commands can generate E749 on startup when placed in a vimrc if the bars are not properly encoded or escaped. [1]. Document this failure mode and synonym near the generated error, and cross link with :help :bar. Note that one must read or scroll quite a bit to find the mention of :| behaving like :print! [1]: https://vi.stackexchange.com/q/46625/10604 closes: vim/vim#17173 https://github.com/vim/vim/commit/187df69fd1563535773b8ddb2de1b0f5dd3dd2e9 Co-authored-by: D. Ben Knoble <ben.knoble+github@gmail.com>
Diffstat (limited to 'runtime/lua/_vim9script.lua')
0 files changed, 0 insertions, 0 deletions