Development announce

[Shougo]

Hi, users.

I will create new completion plugin for neovim.
It is deoplete.nvim (Dark powered nEO comPLETE).

if_python3 plugins are supported in neovim.
So, it is time to development.

I will release first alpha version of deolpete.nvim in May.
But it is not useful plugin.
It is just concept.

I will create "buffer" source in first.

And I will backport some completion patches in Vim to neovim.
This is needed for deoplete asynchronous.

[faceleg]

Great! Thanks @Shougo!

[Shougo]

:-)

[ghost]

Very exciting... what patches need to be back ported @Shougo?

On April 28, 2015 4:08:14 AM EDT, Shougo notifications@github.com wrote:

:-)

---

Reply to this email directly or view it on GitHub:
#2 (comment)

[Shougo]

@pyrohh They are Vim 7.4.630, 7.4.633, 7.4.653. If you backport the patches, I can reduce the works...

[Shougo]

The patches fix complete() bugs in Vim. I use complete() for neocomplete and deoplete.
It is important.

[jochenvdv]

👍

[Shougo]

neovim/neovim#2524

Vim 7.4.630 is backported!

[Shougo]

After the backport is finished, I will backport some patches for completion in vim_dev.
It also important.

For example:

Patch to add v:completed_item. (Shougo Matsu, 2013 Nov 29).
Patch to add 'completeselect' option.  Specifies how to select a candidate in
insert completion. (Shougo, 2013 May 29)
Update to add to existing 'completeopt'. 2013 May 30

[moonstruck]

This is great news. Thanks.

[Shougo]

neovim/neovim#2526

Vim 7.4.633 is backported.

[w0ng]

Awesome news. A decent completion plugin is what's keeping me from using neovim.

[hoschi]

Great 👍

[jakubgs]

Thank G... Shougo!

[khalidchawtany]

👍 I love anything you build 😍

[ghost]

👍 @Shougo is awesome!

[Shougo]

I have started development....
I will push the first version today.
But it is just mock.

[Shougo]

neovim/pynvim#111 is needed for deoplete.nvim.

[Shougo]

I pushed the first commit.

[bluddy]

Very excited! Great job Shougo!

[faceleg]

This is the vim project I've been most excited about this year!

[blueyed]

Will you use jedi for Python completion? (see also https://github.com/davidhalter/jedi-vim)

Have you thought about using ycmd as completion server? (Used by YouCompleteMe)

[Shougo]

Will you use jedi for Python completion? (see also https://github.com/davidhalter/jedi-vim)

Not in plan. But deoplete can add sources by users. Users can add for jedi source.

Have you thought about using ycmd as completion server? (Used by YouCompleteMe)

No.

[ianks]

Yay!

[blueyed]

@Shougo
Then take a look at https://github.com/Valloric/ycmd maybe.

And as for Jedi, that would be a good default for Python I think.

[faceleg]

@blueyed I don't want to have to compile code to get a completion plugin working. I strongly believe I am not alone in this.

[ghost]

agreed, please no compilation.

[blueyed]

There's no compilation needed for Jedi, and ycmd would be optional of course anyway, but provides great completion for compiled languages (C-family, C#, and Go).
ycmd uses Jedi itself, but that could be used directly then.

[Shougo]

I don't add ycmd support in deoplete. But other people may add ycmd source.
I don't limit it.

[Shougo]

Have you thought about using ycmd as completion server? (Used by YouCompleteMe)

If you want to complete by ycmd, you should use YouCompleteMe.

[wsdjeg]

can not open the link, are you ok?

[Shougo]

Yes, I can open it.

[wsdjeg]

ok boresome GFW，

[Shougo]

Oh, ...

[wsdjeg]

nothing can prevent me from using deoplete 😆 😃

[wsdjeg]

waitting for :
deounite (Dark powered nEO unite)
deosnippet (Dark powered nEO snippet)
deobundle (Dark powered nEO neobundle)
mayby it is deoin

[Shougo]

deounite (Dark powered nEO unite)

Please wait...

deosnippet (Dark powered nEO snippet)

Nothing. But neosnippet will be refactored.

deobundle (Dark powered nEO neobundle)

It is dein.vim(Dark powered nEo plugIN manager)

[wsdjeg]

hi @Shougo from neovim/neovim#795
I saw you say If neovim does not support libcall, I don't want to use/support neovim.
now the neovim has a lot diff with vim ,also you plugin deoplete only can be used in neovim ,does it means ,you recommend us use neovim instead of vim ?

[Shougo]

now the neovim has a lot diff with vim ,also you plugin deoplete only can be used in neovim ,does it means ,you recommend us use neovim instead of vim ?

It is difficult question.
Current neovim has 100 over unmerged patches from Vim.
neovim must include most of Vim features.

If neovim has most of Vim features and a lot of original features, OK.
I want to use neovim as the main editor.

[wsdjeg]

hope neovim has all the features of vim,but better,I lso want to use neovim as main editor even if IDE!
now I am following you and your plugin
by the way,I think neovim needs more user and contributers

[Shougo]

by the way,I think neovim needs more user and contributers

Yes, neovim needs more man power than Vim to implement more features than Vim.
But current neovim is the same man power with Vim...

[wsdjeg]

Is there any feature of vim will be deleted in neovim? such as libcall.
and I think asynchronous also can be implemented in vim ,issue of JC2 ,but I think it is different with deoplete.

when will the lua-client of neovim been been finished?if it works well,will neocomplete also can works in neovim?

[Shougo]

Is there any feature of vim will be deleted in neovim? such as libcall.

libcall is not deleted. It is reimplemented.
I think re-implementation is important.
For example: GUI, Windows support, if_lua etc.

and I think asynchronous also can be implemented in vim ,issue of JC2 ,but I think it is different with deoplete.

Yes. The asynchronous is available in Vim. But it is ugly hack and needs the external processes(or the external interfaces) and it is partial of the completion.
Deoplete's asynchronous is the whole complete routine.

when will the lua-client of neovim been been finished?if it works well,will neocomplete also can works in neovim?

Yes, it works. But deoplete is better.
If neovim supports if_lua, unite will be faster. It is important for me.

[wsdjeg]

thanks,I got it.

[sharethewisdom]

Could vim-ledger's omnicompletion be defined in g:deoplete#sources.ledger? I would like to use deoplete to define ':' to automatically show the omnicomplete menu, listing accounts.

[Shougo]

@sharethewisdom
This is not the question site....

let g:deoplete#omni#input_patterns={}
let g:deoplete#omni#input_patterns.ledger = ':\w*'

[tony]

How do you disable buffer completion / the suggestions with [B] next to it?

Is there an equivalent in deoplete for:

call neocomplete#custom#source('buffer', 'disabled', 1)
call neocomplete#custom#source('vim', 'disabled', 1)

[Shougo]

@tony
:help g:deoplete#ignore_sources

[tony]

@Shougo I already had that open, but the documentation is missing an example.

[Shougo]

@tony Added.

[cazador481]

@Shougo I added deoplete sources for perlomni. https://github.com/c9s/perlomni.vim On your next update you can add as source material for deoplete

[Shougo]

@cazador481 Thank you. Updated the documentation.

[wsdjeg]

@Shougo would you add an option for disable the completion in comments or string,just like

g:ycm_complete_in_comments
g:ycm_complete_in_strings

[Shougo]

No. Because, to check it is slow.
The source can check it though.

[wsdjeg]

ok,I know,thanks

[wsdjeg]

will this project support vim8？

[Shougo]

https://github.com/Shougo/deoplete.nvim/blob/master/doc/deoplete.txt#L981

[ViViDboarder]

Since the documentation has changed, that link now points to a random line. Here is a fixed version with a line number:

deoplete.nvim/doc/deoplete.txt

Line 987 in d53c8f4

VIM8 ASYNC API SUPPORT *deoplete-vim8*