aboutsummaryrefslogtreecommitdiff
path: root/runtime/lua/vim/_meta/api_keysets.lua
diff options
context:
space:
mode:
authorglepnir <glephunter@gmail.com>2025-04-26 13:06:43 +0800
committerglepnir <glephunter@gmail.com>2025-04-27 15:00:31 +0800
commitfcabbc2283c5d217d879d4ac0cc6c8501f15fc64 (patch)
treee7b0dede1eaefc147cb8087f36a9cc4ec27e1129 /runtime/lua/vim/_meta/api_keysets.lua
parentac8ae1596cda8a96af0c26046463ba6327cfb0f8 (diff)
downloadrneovim-fcabbc2283c5d217d879d4ac0cc6c8501f15fc64.tar.gz
rneovim-fcabbc2283c5d217d879d4ac0cc6c8501f15fc64.tar.bz2
rneovim-fcabbc2283c5d217d879d4ac0cc6c8501f15fc64.zip
vim-patch:9.1.1341: cannot define completion triggers
Problem: Cannot define completion triggers and act upon it Solution: add the new option 'isexpand' and add the complete_match() function to return the completion matches according to the 'isexpand' setting (glepnir) Currently, completion trigger position is determined solely by the 'iskeyword' pattern (\k\+$), which causes issues when users need different completion behaviors - such as triggering after '/' for comments or '.' for methods. Modifying 'iskeyword' to include these characters has undesirable side effects on other Vim functionality that relies on keyword definitions. Introduce a new buffer-local option 'isexpand' that allows specifying different completion triggers and add the complete_match() function that finds the appropriate start column for completion based on these triggers, scanning backwards from cursor position. This separation of concerns allows customized completion behavior without affecting iskeyword-dependent features. The option's buffer-local nature enables per-filetype completion triggers. closes: vim/vim#16716 https://github.com/vim/vim/commit/bcd5995b40a1c26e735bc326feb2e3ac4b05426b Co-authored-by: glepnir <glephunter@gmail.com>
Diffstat (limited to 'runtime/lua/vim/_meta/api_keysets.lua')
0 files changed, 0 insertions, 0 deletions