the order of the plugins matters

[xnhp0320]

It should be ordered exactly as following:

Plug 'prabirshrestha/asyncomplete.vim'
Plug 'prabirshrestha/vim-lsp'
Plug 'prabirshrestha/asyncomplete-lsp.vim'

I used the vim-lsp first so I placed the vim-lsp in front of asyncomplete, and this causes issues:

when you type for exmaple:

import std.al

the popup menu shows algorithm, and you choose algorithm, however the texts become:

import std.alalgorithm;

in a word, the autocomplete will not trim the prefix but append the whole word.

I do not think this is a big problem, but I think it should be mentioned in the readme doc, it is really annoying and hard to find the cause.

[MLackner]

Hi! I'm experiencing the same problem. Tried your suggestion but that did not help. Are you sure this was the problem? I'm also using vim-plug for plugin management.

Edit: Turns out I am not able to modify the load order. Despite having this in my config:

Plug 'prabirshrestha/asyncomplete.vim'
Plug 'mattn/vim-lsp-settings'
Plug 'prabirshrestha/vim-lsp'
Plug 'prabirshrestha/asyncomplete-lsp.vim'

I checked the load order with echomsg 'loading <plugin> ... and it turns out the load order is as follows:

loading lsp_settings.vim ...
loading asyncomplete-lsp.vim ...
loading lsp.vim ...
loading asyncomplete.vim ...

Any idea how I can force the correct load order? vim-plug suggests just ordering the plugins in the .vimrc file defines the load order. Apparently this does not work.

[xnhp0320]

I do not know, maybe replace the vim-lsp-settings into the other places?