chemzqm
Re:Coc.nvim – Intellisense Engine for Vim8 and Neovim
on Saturday March 30, 2019 @06:45PM (#19532429)
Let me tell you why coc.nvim is created.
I used to use deoplete.nvim, LanguageClient-neovim with javascript-typescript-stdio, but they easily broken lots of time everyday and debug the problems is also quite challenging. So I made it to be able to load fork of vscode extension, and coc-tsserver implemented more than 95% features that vscode could provide. It's not easier to switch vim plugins, consider come back when you would like to try out some new features.
Re:Coc.nvim – Intellisense Engine for Vim8 and Neovim
on Saturday March 30, 2019 @06:33PM (#19532372)
The big advantage of ALE is it has much more linters.
The big advantage of coc.nvim is it can load extensions forked from VSCode, which have more features most of the time.
You can use both of them as the same time, and coc support send diagnostics to ALE.
Re:Coc.nvim – Intellisense Engine for Vim8 and Neovim
on Saturday March 30, 2019 @06:25PM (#19532332)
The problem most people have to code with other libraries, and the intellisense can help to make the work easier.
It also helps you to make better code by showing diagnostics.
Images preview component for web pages on touch device
Re:Fish Shell Design Principles
on Wednesday February 17, 2016 @02:17AM (#11115955)
Thanks for sharing, I do like the philosophy that avoiding esoretic syntax and unnecessary configuration, that would prevent anyone from writing clean and solid code.