vim-dispatch

Yep. I have formatters and linters run on save in vim (of course, any editor or IDE can handle this) and the linters render their results in vim, as well. I also use vim-dispatch [0] to handle running builds and test suites asynchronously, but I don't run any auto commands for that, instead preferring to kick those tasks off with a keystroke. My workflow is crafted in a way to give me, what I have found to be, the tightest feedback loop that I can possibly get with the languages and frameworks and tooling that I use at work. I find that vim, out of every other editor or IDE that I've ever used, is set apart in it's ability to deliver on that requirement. [0]: https://github.com/tpope/vim-dispatch

async VIM - We had it 4 years ago with VIM-Dispatch. https://github.com/tpope/vim-dispatch

Not posting to cause drama BUT: > I case you don’t know neovim yet, it is an awesome fork of vim with several enhancements, such as built-in terminal emulator and asynchronous jobs. Vim has had asynchronous jobs before the fork. For example: https://github.com/tpope/vim-dispatch built-in terminal emulator: Why just do this in vim - noremap <C-d> :sh<cr> <C-d> goes into and out between vim and your shell. What am I missing?

Have you seen dispatch.vim? It makes it easy to dispatch commands from Vim to a tmux split, etc. https://github.com/tpope/vim-dispatch

This. I've seen my teammates try other Go IDE integrations but this just beats the pants off all of them and our whole team wound up standardizing on it. It combines well with Tim Pope's dispatch plugin for doing an async 'go build' or 'go test' while you code: https://github.com/tpope/vim-dispatch

I am actually using vim-dispatch[1] that works fairly well. [1] https://github.com/tpope/vim-dispatch

WTF are you talking about? Vim have may have many demerits but segfaults is not on that list. If segfaults are that frequent you described then people would have jumped ship already. I can't comment on the code structure of Vim but it does not matter to me because end product is working fine for me for 5+ years. Also bad code structure did not stop continuous development of Vim. Just for example there were 1000 patches added to the core before Vim version was changed from 7.3 to 7.4 within 2 years. Important features like more python binding, lua bindings were added during this time. Even if you see the current patch log of 7.4 ftp://ftp.vim.org/pub/vim/patches/7.4/README 68 patches were added since 7.4 release. Though async future is not built-in there are several plugins for doing async operation, for example vim-dispatch[1] and vimproc

Thanks for pointing this out! But I think you meant https://github.com/tpope/vim-dispatch.