aboutsummaryrefslogtreecommitdiff
path: root/runtime/lua/vim/range.lua
diff options
context:
space:
mode:
authorJan Edmund Lazo <janedmundlazo@hotmail.com>2026-08-15 22:28:08 -0400
committerJan Edmund Lazo <janedmundlazo@hotmail.com>2026-08-16 22:23:06 -0400
commitcd71a1358902ac640b0feeda649c335af7a983a8 (patch)
treeb8c70765e2f090cabc7614c2645f03974d1a8efb /runtime/lua/vim/range.lua
parent19a7f26a9cad60a695839562e8a718fa60f7d4c3 (diff)
downloadrneovim-cd71a1358902ac640b0feeda649c335af7a983a8.tar.gz
rneovim-cd71a1358902ac640b0feeda649c335af7a983a8.tar.bz2
rneovim-cd71a1358902ac640b0feeda649c335af7a983a8.zip
build(vim-patch): auto-n/a refactor patch like v8.2.0514
Follow-up refactor patches, mixed with unrelated patches in the middle, is normal in vim-dev when the original patch is not fully tested across all builds via CI or reviewed by others. Unless core maintainers push "vim-patch:" directly to master/main branch without running the full test-suite, there is little reason to merge incomplete ports that will fail on Nvim's CI or code review. Relevant changes in patches like v8.2.0514 are either ported or (will) become N/A.
Diffstat (limited to 'runtime/lua/vim/range.lua')
0 files changed, 0 insertions, 0 deletions