7 ms·
I personally prefer https://github.com/dense-analysis/ale https://github.com/dense-analysis/ale plugin. It is in vimscript and supports almost everything (inclu
by vyskocilm 6y ago
I personally prefer https://github.com/dense-analysis/ale https://github.com/dense-analysis/ale plugin. It is in vimscript and supports almost everything (including clangd) out there: https://github.com/dense-analysis/ale/blob/master/supported-tools.md https://github.com/dense-analysis/ale/blob/master/supported-...
- tylerscott 6y ago+1 for Ale. It has simplified my Vim life.
- f00zz 6y agoI've been using syntastic [1] for this. No server needed. [1] https://github.com/vim-syntastic/syntastic https://github.com/vim-syntastic/syntastic
- glennvtx 6y agoSame here
- gen220 6y agoIs there some feature that coc.vim has that ale does not? Can someone explain coc.vim's popularity to me? I don't understand why coc.vim is so popular, when Ale is so performant and "debuggable" (i.e. produces useful performance traces). [long-time ale user here, I don't use clangd but I do use python-language-server, which is similar]
- jswny 6y agoGenerally it's because Coc has completion, snippets, and pretty much everything from the regular VSCode version of the extension built-in, so Coc can replace multiple plugins, and it works very well.
- gen220 6y agoRight, but Ale does this too (replace multiple plugins, supports completion, linting/formatting). Is it that coc.vim doesn't make you install the binaries of the tools (i.e. go-pls, python-language-server, clangd)? If so, that would be enough to explain the popularity to me. IMO, one could make the argument that it's somewhat antithetical to vim-culture, to not understand the non-vim binaries your editor is executing.
- colordrops 6y agoDo you understand how Ale works? I use Vim not for philosophical or cultural reasons but because I enjoy the UX. CoC's autocompletion is much more advanced than Ale. I used Ale for years.
- gen220 6y ago> CoC's autocompletion is much more advanced than Ale I thought that both are pass-throughs to other completion engines, so isn't this a moot comparison? (maybe coc integrates the completion engine, but it doesn't implement a new one, right?). I use deoplete, but I'm not married to it (it's kind of slow when you have a big file). let g:deoplete#enable_at_startup = 1 call deoplete#custom#option({ \'auto_complete_delay': 1000, \'sources': { \ '_': ['ale', 'buffer'], \ 'py': ['ale'], \} \}) If so, isn't the completion experience is strictly a function of the completion engine you're passing coc/ale into (ux), and the binaries that you're passing into coc/ale (completion options)?
- colordrops 6y agoCoC is built around the Microsoft Language Server. I wasn't able to get LSP working with Ale but perhaps things have changed since I switched.
- vyskocilm 6y agoMicrosoft Language Server is a protocol. It's up to each language to have own , blessed implementation like clangd, solargraph, or gopls. The beauty of ale plugin is that it supports almost anything from scratch and as I work on a multi language projects all the time it rocks everywhere. Do you have prettier installed? Boom all your JS files are checked. Do you have gopls, gofmt, goimports? Then yeah, you can use all of those from your editor. And so on. I am usually surprised how many linters it supports. Recently I got hints when editing protobuf file. Did not expected it. It is possible that coc.vim can do better. But I can't imagine how much better it should have be.