Is this extension in a usable state?

[dpriedel]

I've been using vim 8.1 with coc and ccls for a while now and find it a very productive combination.

I saw this extension and thought I would give it a try. After installing it and openning a .cpp file with vim, nothing happens. ccls is not started and there is nothing in CocInfo nor the coc log file.

Am I missing something basic?

Thanks

[Maxattax97]

Haha, yeah it's totally not done yet, still in pre-release version (0.0.4 as of writing) :sweat_smile:. There aren't a ton of COC extensions built by anyone other than the guy who made COC itself, so it's hard to figure out what it takes to get one working.

I got about this far and tried to figure out whether or not it was actually worth it since the equivalent VSCode extension doesn't offer lots of additional tools. I'd like to come back to it, but I'm finishing up my final year of University, so until May I won't be devoting much to it. I write lots of C in Neovim at work though, so I have incentive to come back.

I'll leave this issue open and notify you after I hit first release, then close it. It's pleasant to hear that there's interest in my humble fork. :+1:

[dpriedel]

Thanks and good luck with your studies !!

[DwordPtr]

Second that. I also write C in Neovim for my dayjob. Really excited for this to hit release.

[dpriedel]

Second that. I also write C in Neovim for my dayjob. Really excited for this to hit release.

Are you aware that you can run ccls (and other LSs) directly from coc?

just add the following to your CocConfig and ccls runs great !

{ "languageserver": { "ccls": { "command": "ccls", "filetypes": ["c", "cpp", "cuda", "objc", "objcpp"], "rootPatterns": [".ccls", "compile_commands.json", ".vim/", ".git/", ".hg/"], "initializationOptions": { "cache": { "directory": "/tmp/ccls-cache", "retainInMemory": 1 } } } }, }

[oblitum]

@dpriedel but it's nonetheless great to have a extension that could provide additional goodies and ccls binaries packaged.

[listerreg]

I'm sorry but you could have note it in the description on https://www.npmjs.com/package/coc-ccls. For the second time I'm falling for it. Why is it there anyway?

[oblitum]

@listerreg just watch this issue and only install it again when it gets closed. I agree it's best that it would be removed from npmjs while not usable, but you should notice that coc.nvim doesn't recommend it at the moment, just raw ccls language server configuration.

[Maxattax97]

@oblitum I investigated removing the package because i wanted to leave room for someone else to take the package name if they felt so inclined; however, it appears the name is now unfortunately forever locked to me: https://docs.npmjs.com/cli/unpublish

I could deprecate it, but I think I'll save that for if someone makes another coc-ccls so that I can redirect to it. That being said, the semver does indicate it's pre-release.

I've updated the README and published a "patch" to NPM, per @listerreg's request.

If I get some time I think it might make sense to make this a "dumb" extension which:

• automatically uses the settings from the coc.nvim wiki for CCLS
• automatically downloads the appropriate CCLS binary for the user's platform

Because I can't see a ton of features being useful from the VS Code version of this.