You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Shipping completers in external repository would allow users to reuse the server piece and add more features such as go to definition, rename. Useful for completions provided by Language Server Protocol such as typescript server. This would also mean only one instance of the server is running to provide IDE like features.
I think only some of the completers such as buffer, files should ship by default similar to how depoplete does it.
The text was updated successfully, but these errors were encountered:
@maralla any updates on this? I plan to add completion support via vim-lsp and nvim-langserver-shim and would really love to use completor.vim due to its simplicity and the fact that it just works.
What are your thoughts on completor.vim being able to use pure vimscript to provide completions without python as an alternative?Also would love to an option to provide completions in completor.vim without completor.vim managing the jobs. It would be delegated to other libraries such as nvim-languageserver-shim. Currently vim-lsp and nvim-languageserver-shim works in pure vim script without python so would love to have the same for completor.vim. This would also give option to either write completors in pure vim script or python and would not break the existing ecosystem.
Shipping completers in external repository would allow users to reuse the server piece and add more features such as go to definition, rename. Useful for completions provided by Language Server Protocol such as typescript server. This would also mean only one instance of the server is running to provide IDE like features.
I think only some of the completers such as buffer, files should ship by default similar to how depoplete does it.
The text was updated successfully, but these errors were encountered: