4 ms·

Looks like Spacemacs [1], but for vim. Spacemacs has a more thorough "what is this." Emacs is best thought of as a lisp virtual machine that happens to edit te

Looks like Spacemacs [1], but for vim. Spacemacs has a more thorough "what is this." Emacs is best thought of as a lisp virtual machine that happens to edit text. Vim is a hell of a text editor that happens to have a Turing complete scripting language. Spacemacs gives emacs a good text editor, while it looks like Spacevim is attempting to make extending vim easier. The future of emacs and vim as platforms is interesting. Perhaps, at least for developer tools, we'll see more projects using these cross platform text editors as platforms for text based user interfaces in a revolt against electron. [1] https://www.spacemacs.org https://www.spacemacs.org

themodelplumber 8y ago
> we'll see more projects using these cross platform text editors as platforms for text based user interfaces in a revolt against electron. Wow, I did not anticipate this comment ending this way.
ageofwant 8y ago
"revolt against electron" who even uses that hippy shit ? vim for life and after .-=-. / + \ | ~~~ | | :wq!| |_____|
- fxfan 8y ago
  As a vim user, please don't give the rest of us a bad name ;). You're sounding like a hippy :)
fxfan 8y ago
I like your explanation of emacs and vim. Btw, neovim natively talks async using msgpack meaning plugins can be written in any language (with glue in vimscript)
bpye 8y ago
I don't like the trend of Electron being used anywhere but I've really struggled to match my productive in VS Code in Vim or Spacemacs. I've certainly tried! I even spent a month or two last year using exclusively OpenBSD and nvi as a bit of an experiment - I did enjoy how quick my text editor opened for example, but I am still a lot more productive in Code. Any suggestions for someone wanting to learn without their productivity taking a dive? Maybe finding a Vim plugin for my existing editor and learning there before switching to "real" vim... I'm not sure.
- didibus 8y ago
  For spacemacs, I'd recommend you try it again in Holy mode with Ivy. Then slowly customize some of it to add some features and key bindings to your liking that make you more productive. Emacs really clicks if you are someone whose going to learn your way around Emacs lisp and customize things to what works best for your style. And make sure you use the develop branch. Once you've groked that, you can slowly try to switch to Evil bindings, and explore if you enjoy modal editing or simply get some inspiration from the Vim editing commands and style.

themodelplumber 8y ago

> we'll see more projects using these cross platform text editors as platforms for text based user interfaces in a revolt against electron. Wow, I did not anticipate this comment ending this way.

ageofwant 8y ago

"revolt against electron" who even uses that hippy shit ? vim for life and after .-=-. / + \ | ~~~ | | :wq!| |_____|

fxfan 8y ago
As a vim user, please don't give the rest of us a bad name ;). You're sounding like a hippy :)

fxfan 8y ago

I like your explanation of emacs and vim. Btw, neovim natively talks async using msgpack meaning plugins can be written in any language (with glue in vimscript)

bpye 8y ago

I don't like the trend of Electron being used anywhere but I've really struggled to match my productive in VS Code in Vim or Spacemacs. I've certainly tried! I even spent a month or two last year using exclusively OpenBSD and nvi as a bit of an experiment - I did enjoy how quick my text editor opened for example, but I am still a lot more productive in Code. Any suggestions for someone wanting to learn without their productivity taking a dive? Maybe finding a Vim plugin for my existing editor and learning there before switching to "real" vim... I'm not sure.

didibus 8y ago
For spacemacs, I'd recommend you try it again in Holy mode with Ivy. Then slowly customize some of it to add some features and key bindings to your liking that make you more productive. Emacs really clicks if you are someone whose going to learn your way around Emacs lisp and customize things to what works best for your style. And make sure you use the develop branch. Once you've groked that, you can slowly try to switch to Evil bindings, and explore if you enjoy modal editing or simply get some inspiration from the Vim editing commands and style.