Results 55 comments of Mal

Update both `completor.vim` and `completor-neosnippet` to the latest commit will fix the problem.

What is the commit id of completor you have installed? What is the result of `:echo &completeopt`?

My environment can not produce this problem. So can you please disable all other plugins and only enable completor.vim and comment out all configurations to construct a minimal environment to...

The commit ed06e70ba0134d9265bf9ca560d166dbab6d1fce added the ability to jump to placeholders. Use `tab` to jump to placeholder: ```vim map CompletorCppJumpToPlaceholder imap CompletorCppJumpToPlaceholder ```

I think it will work by just adding the file type map config. I tried with the following config for my environment: ``` vim let g:completor_filetype_map = {} let g:completor_filetype_map.javascript...

This will be fixed by kyouryuukunn/completor-necovim#1.

I think it's better to implement this in a different repo. Here are the examples of implementing completers in its own repo: * [swift support](https://github.com/maralla/completor-swift) * [neosnippet support](https://github.com/maralla/completor-neosnippet)

You can add the following config to disable refresh on every input: ```vim let g:completor_refresh_always = 0 ```

Updating to the latest commit and setting the following trigger may fix the problem: ```vim let g:completor_javascript_omni_trigger = "\\w+$|[\\w\\)\\]\\}\'\"]+\\.\\w*$" ```

Currently the omnicomplete results are computed using the current vim instance synchronously. And right now I can't find a proper way to do this asynchronously. So maybe it's better to...