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
The documentation states that setting autoComplete to false will automatically set omniComplete to true, and omnifunc will be set. However, this does not work as expected when LspOptionsSet is called after LspAddServer. The documentation should clarify the required order of calling LspOptionsSet and LspAddServer. Alternatively, the code should ensure omniComplete is set correctly after LspOptionsSet is called, or even better, refactor LspAddServer to accept LSP options as an argument.
The text was updated successfully, but these errors were encountered:
nv-quan
changed the title
omniComplete is not set to true when LspOptionsSet is called after LspAddServeromnifunc is not set when LspOptionsSet is called after LspAddServerJun 17, 2024
This was discussed already a couple of times, say in https://github.com/yegappan/lsp/pull/442/files and e3216ca, and 87189fa ;
the doc now states the correct order of calling LspOptionsSet and LspAddServer.
However, I'd agree that it would make users' life simpler if the importance of this order was drawn to attention.
The documentation states that setting
autoComplete
to false will automatically setomniComplete
to true, andomnifunc
will be set. However, this does not work as expected whenLspOptionsSet
is called afterLspAddServer
. The documentation should clarify the required order of callingLspOptionsSet
andLspAddServer
. Alternatively, the code should ensureomniComplete
is set correctly afterLspOptionsSet
is called, or even better, refactorLspAddServer
to accept LSP options as an argument.The text was updated successfully, but these errors were encountered: