4 ms·

No, vim does not have anything that comes close to the killer feature (and only good feature) of Emacs: lisp.

pyre 11y ago
I switched back to Vim from Spacemacs, because many of the features that I like about Vim seem more "solid." In Emacs, the environment can vary widely depending on your major mode, and several times I would end up in states that I did not know how to rectify without a full Emacs restart (to be fair these breakages were with evil-mode). Like another poster said, there are so many things in Emacs that are half-baked and/or don't play well with other popular extensions. It's really annoying. I wanted to like Emacs, but I'm finding a better experience with Vim. Edit: As an example of breakages with evil-mode, sometimes evil-mode would end up in a state where pressing 'd' once in normal mode would delete the whole line (which is supposed to be bound to 'dd') and I was unable to access any other combinations with 'd' as a result (e.g. 'd$' to delete to the end of line). It was annoying and happened fairly often, but was not reproducible (as in 'on demand') for me. IIRC, this spanned all buffers and I just had to restart Emacs to fix it.
- jbssm 11y ago
  My thoughts exactly. Coming from Vim I really wanted to like the idea of some fully async editor with Vim ease of navigation and Emacs power packages (org mode, async repl like iPython, etc) so I found the idea of Spacemacs awesome. But in practice it's just too broken, after almost 2 days where I fully dedicated my time to do something as simple as showing line numbers in a consistent way, showing the Git gutter and showing the syntax checker marks in the gutter and being unable to solve the issue, I just gave up. Mind you, this is just a small thing that should work right away (and does work right away in Vim), but seems impossible in Emacs because the packages just don't play nicely with each other. Worst, asking for help in Stackoverflow amounts to nothing, seems like the Emacs/Spacemacs just has their config and they don't want to touch it afraid to break it. The open bugs in Github for many of the troubles in Space are just mostly closed without an answer (really, for instance getting the theme colors to actually work in a terminal in OSX is a nightmare and nobody cares about it and the devs just close the bugs without solution). Still, I'm still thinking about giving one last effort of just ditching Spacemacs and try to config Emacs from origin with evil mode and build from there, let's see. BRIGHT SIDE: The philosophy being Spacemacs is really nice tough. I've been changing my Vim config to use a consistent approach to the <LEADER> keybindings and it's really productive and intuitive. I just which there was some package that allowed to see the available keybindings in a small window at the bottom in Vim like you do in Spacemacs. That would be absolutely great.
- khgvljhkb 11y ago
  I agree with you. Being a former heavy vim user, now using Emacs, I miss vim every day. Spaceemacs wasn't for me, so I now have a modified Emacs Prelude. I was more effective with vim, but Emacs being a lisp is just hard to beat for me. Here's to wishing for a better sort of programmers environment...

pyre 11y ago

I switched back to Vim from Spacemacs, because many of the features that I like about Vim seem more "solid." In Emacs, the environment can vary widely depending on your major mode, and several times I would end up in states that I did not know how to rectify without a full Emacs restart (to be fair these breakages were with evil-mode). Like another poster said, there are so many things in Emacs that are half-baked and/or don't play well with other popular extensions. It's really annoying. I wanted to like Emacs, but I'm finding a better experience with Vim. Edit: As an example of breakages with evil-mode, sometimes evil-mode would end up in a state where pressing 'd' once in normal mode would delete the whole line (which is supposed to be bound to 'dd') and I was unable to access any other combinations with 'd' as a result (e.g. 'd$' to delete to the end of line). It was annoying and happened fairly often, but was not reproducible (as in 'on demand') for me. IIRC, this spanned all buffers and I just had to restart Emacs to fix it.

jbssm 11y ago
My thoughts exactly. Coming from Vim I really wanted to like the idea of some fully async editor with Vim ease of navigation and Emacs power packages (org mode, async repl like iPython, etc) so I found the idea of Spacemacs awesome. But in practice it's just too broken, after almost 2 days where I fully dedicated my time to do something as simple as showing line numbers in a consistent way, showing the Git gutter and showing the syntax checker marks in the gutter and being unable to solve the issue, I just gave up. Mind you, this is just a small thing that should work right away (and does work right away in Vim), but seems impossible in Emacs because the packages just don't play nicely with each other. Worst, asking for help in Stackoverflow amounts to nothing, seems like the Emacs/Spacemacs just has their config and they don't want to touch it afraid to break it. The open bugs in Github for many of the troubles in Space are just mostly closed without an answer (really, for instance getting the theme colors to actually work in a terminal in OSX is a nightmare and nobody cares about it and the devs just close the bugs without solution). Still, I'm still thinking about giving one last effort of just ditching Spacemacs and try to config Emacs from origin with evil mode and build from there, let's see. BRIGHT SIDE: The philosophy being Spacemacs is really nice tough. I've been changing my Vim config to use a consistent approach to the <LEADER> keybindings and it's really productive and intuitive. I just which there was some package that allowed to see the available keybindings in a small window at the bottom in Vim like you do in Spacemacs. That would be absolutely great.
khgvljhkb 11y ago
I agree with you. Being a former heavy vim user, now using Emacs, I miss vim every day. Spaceemacs wasn't for me, so I now have a modified Emacs Prelude. I was more effective with vim, but Emacs being a lisp is just hard to beat for me. Here's to wishing for a better sort of programmers environment...