mirrors/neovim
1
0
Fork 0
mirror of https://github.com/neovim/neovim.git synced 2026-05-03 12:35:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

vim-patch:9.1.1409: using f-flag in 'complete' conflicts with Neovim

Browse Source 
Problem:  using f-flag in 'complete' conflicts with Neovims filename
          completion (glepnir, after v9.1.1301).
Solution: use upper-case "F" flag for completion functions
          (Girish Palya).

fixes: vim/vim#17347
closes: vim/vim#17378

14f6da5ba8

Co-authored-by: Girish Palya <girishji@gmail.com>
This commit is contained in:
zeertzjq
2025-05-31 19:03:41 +08:00
parent 13aec582b4
commit eeff6ca8ff
8 changed files with 68 additions and 70 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
runtime/lua/vim/_meta/options.lua generated
View File

@@ -1027,7 +1027,7 @@ vim.bo.cms = vim.bo.commentstring
--- ] tag completion
--- t same as "]"
--- f scan the buffer names (as opposed to buffer contents)
--- f{func} call the function {func}. Multiple "f" flags may be specified.
--- F{func} call the function {func}. Multiple "F" flags may be specified.
--- Refer to `complete-functions` for details on how the function
--- is invoked and what it should return. The value can be the
--- name of a function or a `Funcref`. For `Funcref` values,
@@ -1045,9 +1045,9 @@ vim.bo.cms = vim.bo.commentstring
--- If generating matches is potentially slow, `complete_check()`
--- should be used to avoid blocking and preserve editor
--- responsiveness.
--- f equivalent to using "f{func}", where the function is taken from
--- F equivalent to using "F{func}", where the function is taken from
--- the 'completefunc' option.
--- o equivalent to using "f{func}", where the function is taken from
--- o equivalent to using "F{func}", where the function is taken from
--- the 'omnifunc' option.
---
--- Unloaded buffers are not loaded, thus their autocmds `:autocmd` are