91–100 of 308 posts
Earlier quoted context omitted.
this async thing was Neovim's main selling point, right? I mean cruft-removal is all well and good but vim works fast and fine for me so not important. What does Neovim now offer that this doesn't?
I think neovim just offered us VIM 8.0.
https://danielmiessler.com/study/vim/
Going to download and see what Prezto stuff breaks when I upgrade.
Thanks for the work done here. I'm not a VIM user anymore (I use Spacemacs now), but it opened my eyes/mind to what is a professional code editor. After using VIM, using any other editor feels like programming in Notepad. VIM you'll always be in my heart.
I use Spacemacs for Elixir programming and honestly, Emacs is slow, I would often type commands and then wait for it to complete. I think some reboot like Neovim did for Vim, could be beneficial as it is awesome editor, but it is just too slow to start and slow to use. It might be that Spacemacs layer is adding additional complexity, and maybe going through Helm is the issue, I don't know, just it does take quite a b…
Might see in my tone I am not a fan of this fork.
Thanks for the work done here. I'm not a VIM user anymore (I use Spacemacs now), but it opened my eyes/mind to what is a professional code editor. After using VIM, using any other editor feels like programming in Notepad. VIM you'll always be in my heart.
I use Spacemacs for Elixir programming and honestly, Emacs is slow, I would often type commands and then wait for it to complete. I think some reboot like Neovim did for Vim, could be beneficial as it is awesome editor, but it is just too slow to start and slow to use. It might be that Spacemacs layer is adding additional complexity, and maybe going through Helm is the issue, I don't know, just it does take quite a b…
Perhaps try disabling your layers one at a time to see where the problem is.
Earlier quoted context omitted.
Neovim already fragmented the community. Bram seems to have stepped up to the challenge bigtime since neovim announcement, as judged by his github activity graph. https://github.com/vim/vim/graphs/contributors
I wouldn't say he's stepped up. It's all a reactionary response to Neovim. I dont think we'd ever have async in vim if it weren't for the neovim project. That being said I hope they pull an io.js and merge taking the best of both vim and neovim, whatever that may be.
Earlier quoted context omitted.
I wouldn't say he's stepped up. It's all a reactionary response to Neovim. I dont think we'd ever have async in vim if it weren't for the neovim project. That being said I hope they pull an io.js and merge taking the best of both vim and neovim, whatever that may be.
"Stepped up to challenge" is a reactionary response. Something challenges you, your reaction is to ignore/quit or step up and respond.
Earlier quoted context omitted.
I wouldn't say he's stepped up. It's all a reactionary response to Neovim. I dont think we'd ever have async in vim if it weren't for the neovim project. That being said I hope they pull an io.js and merge taking the best of both vim and neovim, whatever that may be.
async VIM - We had it 4 years ago with VIM-Dispatch. https://github.com/tpope/vim-dispatch
Oh Vim... If you're going to lightweight and vi-like, than do that. If you're going to go the Emacs route (and if you're adding async, packaging, and lambdas, make no mistake, you're starting in the steps to building an inferior Emacs), than get a half-decent extension language. Or just up and die. We don't need a Vi clone that does the Emacs thing, we've got Evil/Spacemacs for that.
> Or just up and die Why would you bash VIM by saying it should die? Just move over to something else and use the "Mom Rule."