Screenshots, Updates, Announcement

[roxma]

Inspired by deoplete.

This issue is a good place to upload screenshots for README.md.

Screenshots shoould not be put into git repo, otherwise it will make the plugin download time much much longer .

Additional tips screenshots will also be published in this issued,

Subscribe this issue if you are interested

[roxma]

All in one screenshot

[roxma]

Triggering Ultisnips or show popup hints with the same key <c-u>

When the expand key is pressed and nothing has been typed, a popup list for snippets will be triggered.

let g:UltiSnipsExpandTrigger = "<Plug>(ultisnips_expand)"
inoremap <silent> <c-u> <c-r>=cm#sources#ultisnips#trigger_or_popup("\<Plug>(ultisnips_expand)")<cr>

[roxma]

Add css completion for inline style attribute:

[roxma]

Added C/C++ code completion with clang_complete

[roxma]

Just implemented a <c-n><c-x><c-n>... like completion source:

https://github.com/roxma/nvim-completion-manager/issues/24#issuecomment-283635150

Pick a key to map to <Plug>(cm_force_refresh)

imap <c-g> <Plug>(cm_force_refresh)

I also have tab mapping

      " smart tab for auto complete
      inoremap <expr> <silent> <Tab>  pumvisible()?"\<C-n>":"\<TAB>"
      inoremap <expr> <silent> <S-TAB>  pumvisible()?"\<C-p>":"\<S-TAB>"

<Tab> for selecting the popup item, <c-g> for refreshing the popup menu. So the key pressed in this screencast is <TAB><c-g><TAB><c-g>...

[roxma]

copied from https://github.com/neovim/neovim/issues/5522#issuecomment-284122091:

Since LanguageClient-neovim already has nice interface, I'm deprecating my previous nvim-cm-php-language-server

Here's a simple php language server package that could be easily setup to work with LanguageClient-neovim, and it is well integrated with nvim-completion-manager

[roxma]

From https://github.com/roxma/nvim-completion-manager/issues/36#issuecomment-284948146:

Just take a deeper look into ultisnips, now parameter expansion works with ultisnips, :smile:

[roxma]

Parameter expandsion for python, javascript, golang, via ultisnips/neosnippet

[SevereOverfl0w]

I have just finished adding NCM support to https://github.com/clojure-vim/async-clj-omni for Fireplace only. Acid.nvim will soon be supported also, once I have performed some refactoring.

This brings Clojure support to NCM.

There is currently no caching of completions, but there is contention between the underlying engine & NCM. I have some ideas of how to bring them together though, so expect caching as an upcoming feature.

[roxma]

Rust completion:

I've been learning rust recently and just implemented a completion plugin based on racer last night. I'm not sure I'm getting racer working the right way. It works but I still miss the macro completion.

https://github.com/roxma/nvim-cm-racer

[roxma]

Thanks to @lervag and @Shougo, vimscript completion is available via neco-vim

[dafufer]

I have added simple Swift completion using sourcekitten: nvim-cm-swift-completer Any suggestion to improve it is welcome

[jsfaint]

gtags complete source gen_tags.vim

[jsfaint]

I added ncm source for neco-syntax Thanks @shougo, the source was already merged into neco-syntax

[jsfaint]

I also add neoinclude support too.

But I'm a little confused about the source priority that which one should be higher? neoinclude(file include) or neco-syntax(language syntax) Currently I give 8 to both of them. neco-syntax mod was already merged to Shougo's repository, but neoinclude mod is not merged yet.

neoinclude screenshot here:

[roxma]

@jsfaint

But I'm a little confused about the source priority that which one should be higher? neoinclude(file include) or neco-syntax(language syntax)

It seems they don't usually apear at the same time. So it doesn't matter.

[jsfaint]

@roxma Got it, thanks for your clarification 👍 I'll create PR for neoinclude

[roxma]

https://github.com/roxma/ncm-github Github completion is added. The idea was borrowed from https://github.com/rhysd/github-complete.vim . thanks to @rhysd and @ahmedelgabri #92

I re-implement it in python, so that the sources should work asynchronously.

[roxma]

let g:cm_matcher = {'module': 'cm_matchers.substr_matcher', 'case': 'smartcase'}

Added sub-string based mathing.

[roxma]

Added a toy project: ncm-phpactor

[roxma]

Another plugin ncm-clang for c/c++ completion. This project deprecates roxma/clang_complete

[roxma]

Adding typescript source: https://github.com/mhartington/nvim-typescript/pull/81

[gaalcaras]

I've created a source for the R language: https://github.com/gaalcaras/ncm-R

Please note that Nvim-R is required for ncm-R to work.

[cyansprite]

support for NCM now CS https://github.com/cyansprite/omnisharp.nvim

[roxma]

I'm sorry to announce that my interest moves to some other projects, due to lack of time I may not update this repo for a long while.

If anyone wants to keep a well-maintained fork, post your link here. I'll put it on top of the README page.

[mfussenegger]

@roxma Do you think ncm stilll has any significant advantages over deoplete to make it worth maintaining it or would you recommend people to move over to deoplete in the long run?

[andreyorst]

@mfussenegger it has advantages over deoplete?

[coachshea]

I think it has advantages of every other completion manager out there. I sincerely hope someone takes it on

-- John Shea Cell: 617-605-5763 Email: [email protected]

On Apr 18, 2018, at 3:15 PM, Andrey Orst [email protected] wrote:

@mfussenegger it has advantages over deoplete?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[nhooyr]

@coachshea not that I do not believe ncm has no advantages, could you elaborate on what the advantages are compared to deoplete?

[coachshea]

@nhooyr, I should have been a little more careful with my language. Of course, I have more experience with some systems than others. I have just loved my experience with ncm and am sad to see it -- possibly -- come to an end. I did try deoplete several years ago and I don't remember specifically why I didn't stay with it. All I do know is that I tried several at the time and chose to stick with YCM. I was by and large happy with YCM and never thought I would try another, but for a variety of reasons, I gave ncm a shot, and I instantly loved it. I made the switch and never (until now) looked back. I'll list some of what I love best about it. It is certainly possible that deoplete, or some other completion manager has similar features and maybe I will have to give it a try again.

First, the start up time is instantaneous. One of my few complaints about YCM was startup time. There are a lot of things I liked about the completions, but maybe most of all was the "on-the-fly" snippet creation. I also loved that you could choose regular or fuzzy completion, and how easy it was for others to create add-ons for other filetypes (I realize that in that regard deoplete is similar).