Hacker News Reader

Comment by bechap | Hacker News Reader

Having seen this article when I first started using vim seriously, I'd recommend fzf.vim in place of ctrl-p and ALE in place of Syntastic. The former I find is much more performant, and the latter takes advantage of Vim8 / neovim's asynchronous features. Plus, fzf.vim comes with Ag, which effectively replaces Ack.vim (albeit, with a little bit of tweaking).

View on HN

The article also recommends neocomplcache, whose github says its deprecated and to use neocomplete, which is also deprecated and suggests you use deoplete. At least the chain ends there for now.

FZF is fantastic, but has anyone managed to make it work in MacVim? I just get weird display corruption and control characters in my search string when I use it.

Works great in the terminal and neovim.app etc.

You can go even further by using FZF+ripgrep, it's so much faster.

I think you can get better results with ctrlp when using cpsm as its matcher. fzf.vim always starts at the top and cpsm actually minds your current file.

That is the reason I chose neomake, because syntastic was dragging vim down. I'm curious, how does ALE compare to neomake?

Using ALE right now. By design: Syntastic runs synchronously on save, Neomake runs asynchronously on save, ALE runs asynchronously as you type. Neomake is good but I see no reason to go back from ALE which works brilliantly.

Neomake can do that too: https://github.com/neomake/neomake#setup

Reply on news.ycombinator.com