Cause vim stuck while typing about asyncomplete-buffer.vim HOT 7 CLOSED

Buffer algorithm is definitely not so good as I would like it to be. If anyone has a better algorithm let me know.

If you have python enabled vim we could also support starting a thread and letting it do much of the computations so vim remains responsive.

from asyncomplete-buffer.vim.

Same here.

Is it possible to exclude certain buffers as references for completion?

I thought about blacklist when registering with asyncomplete#register_source but as far as I understand this is for deactivating all buffer sources for specific filetypes.

from asyncomplete-buffer.vim.

Thanks for your response. I finally decided against buffers as completion source. Apart from long response times, the suggestions by buffers cluttered the completion dialog a lot. I have a much better experience with vim-lsp only.

from asyncomplete-buffer.vim.

I think we should go for the python solution then.

from asyncomplete-buffer.vim.

This is because the TextChangedI causes the buffer source to refresh waaayyyy too often. After #4 is merged, you can override the events in your source registration in .vimrc with something like this:

au User asyncomplete_setup call asyncomplete#register_source(asyncomplete#sources#buffer#get_source_options({
	\ 'name': 'buffer',
	\ 'whitelist': ['*'],
	\ 'blacklist': ['go'],
	\ 'events': ['TextChanged','InsertLeave','BufWinEnter','BufWritePost'],
	\ 'completor': function('asyncomplete#sources#buffer#completor'),
	\ }))

#1 could be solved by this, as well.

from asyncomplete-buffer.vim.

It's perfect now, but I have to explicitly enable let g:asyncomplete_buffer_clear_cache = 1 in vimrc. Cheers! Thanks.

from asyncomplete-buffer.vim.

@tuyenpm9 It defaults to 1

from asyncomplete-buffer.vim.