aboutsummaryrefslogtreecommitdiff
path: root/runtime/lua/vim/_meta/options.lua
diff options
context:
space:
mode:
authorzeertzjq <zeertzjq@outlook.com>2025-01-24 06:44:23 +0800
committerzeertzjq <zeertzjq@outlook.com>2025-01-25 22:39:37 +0800
commit63aa167f944b147b9d4b8c417a37f4beb212d984 (patch)
treefedaaa81b703cc95ff64b40a7f58ede27022ed4b /runtime/lua/vim/_meta/options.lua
parent851137f67905f6038e51b5b7d1490fbedea4faaa (diff)
downloadrneovim-63aa167f944b147b9d4b8c417a37f4beb212d984.tar.gz
rneovim-63aa167f944b147b9d4b8c417a37f4beb212d984.tar.bz2
rneovim-63aa167f944b147b9d4b8c417a37f4beb212d984.zip
vim-patch:9.1.1049: insert-completed items are always sorted
Problem: insert-completed items are always sorted, although the LSP spec[1] standard defines sortText in the returned completionitem list. This means that the server has sorted the results. When fuzzy is enabled, this will break the server's sorting results. Solution: disable sorting of candidates when "nosort" is set in 'completeopt' [1] https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#completionItem closes: vim/vim#16501 https://github.com/vim/vim/commit/f400a0cc41113eb75516bdd7f38aeaa15208ba2c Co-authored-by: glepnir <glephunter@gmail.com>
Diffstat (limited to 'runtime/lua/vim/_meta/options.lua')
-rw-r--r--runtime/lua/vim/_meta/options.lua4
1 files changed, 4 insertions, 0 deletions
diff --git a/runtime/lua/vim/_meta/options.lua b/runtime/lua/vim/_meta/options.lua
index 107b1ffdfb..f0f0d1a768 100644
--- a/runtime/lua/vim/_meta/options.lua
+++ b/runtime/lua/vim/_meta/options.lua
@@ -1098,6 +1098,10 @@ vim.go.cia = vim.go.completeitemalign
--- list of alternatives, but not how the candidates are
--- collected (using different completion types).
---
+--- nosort Disable sorting of completion candidates based on fuzzy
+--- scores when "fuzzy" is enabled. Candidates will appear
+--- in their original order.
+---
--- @type string
vim.o.completeopt = "menu,preview"
vim.o.cot = vim.o.completeopt