aboutsummaryrefslogtreecommitdiff
path: root/test/functional/vimscript/executable_spec.lua
diff options
context:
space:
mode:
authorPhạm Bình An <111893501+brianhuster@users.noreply.github.com>2026-01-29 06:19:20 +0700
committerGitHub <noreply@github.com>2026-01-29 07:19:20 +0800
commitc7c5455da13dc5cab431809c83cbb003d4275c7a (patch)
tree3ec86a78288a1bf4d9632597d85cbfa85442fa9b /test/functional/vimscript/executable_spec.lua
parent41336a35905b4c17978de4bb3be7ba82eb0214b5 (diff)
downloadrneovim-c7c5455da13dc5cab431809c83cbb003d4275c7a.tar.gz
rneovim-c7c5455da13dc5cab431809c83cbb003d4275c7a.tar.bz2
rneovim-c7c5455da13dc5cab431809c83cbb003d4275c7a.zip
vim-patch:1e54023: runtime(doc): clarify vim.eval behavior with Vim special variables (#37369)
Problem: The behavior of vim.eval() with Vim special variables is not clearly documented. It is (partly) the reason why Nvim Python's vim.eval gives different output when evaluating v:true and v:false Solution: Document it (Phạm Bình An) closes: vim/vim#19157 https://github.com/vim/vim/commit/1e54023673f124dcd7339c0c4e0a6d131278baea
Diffstat (limited to 'test/functional/vimscript/executable_spec.lua')
0 files changed, 0 insertions, 0 deletions