Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, vim-lsp-settings is using FileType base event handling. The FileType event is triggered when the filetype is modified from syntax plugins. For example,
*.jl
is registered as filetype=lisp at $VIMRUNTIME/filetype.vim in default. But some users want to use julia with*.jl
. So user install plugin. If a Language Server for common-lisp (ex: cl-lsp) is already installed, vim-lsp-settings start cl-lsp and julia-language-server both. To avoid this, vim-lsp-settings have to make little delay to check the last modified. However, vim-lsp does not have a way to activate Language Server. So this change addlsp#activate
to activate Language Server in lazy.ex: