6 ms·
I have not found this to be the case with Spacemacs. Almost everything you need is bound to keystrokes using space as the leader key in the spirit of vim. As
by mightybyte 10y ago
I have not found this to be the case with Spacemacs. Almost everything you need is bound to keystrokes using space as the leader key in the spirit of vim. As a long-time and fairly advanced vim user I recommend Spacemacs highly.
- maxaf 10y agoDon't you feel like you're pushing a square peg into a round hole? Or do you actually find yourself taking advantage of elisp in harmonious combination with Vim's editing UX?
- Gonzih 10y agoIn my experience it's cleaner than default emacs editing experience, but it's not as clean as you can get in plain vim.
- chm 10y agoI thought the same thing as you at first, as I was a vim+pathogen user. My workflow was working properly but to me it's just much simpler to do a SPC-f-e-d, add 'git' to my packages, then SPC-f-e-R and voila, git support is installed. I'm sure I'll go back some day but for now Spacemacs is perfect for my use (i.e. writing small software, not large projects).
- Gonzih 10y agoI was also using spacemacs for something like 2 month. After that I just rewrote my vim configuration with what I learned from spacemacs in mind. It's great and clean. But it's still emacs and vim emulation. Nowadays i'm much happier with my vim configuration partially thanks to spacemacs.
- tingol 10y agoCan you share the things you took with you? I'm always interested in spicing up my vim experience.
- Gonzih 10y agoMostly key bindings. Space as a leader. Everything themed by prefix. Like <spc>mee to eval clojure form in repl. <scp>mek to show clojure documentation. <spc>cl - comment line. Switched to unite. Duplicated most used things from helm in unite. You can check out my github repo with vim configs at Gonzih/.vim on github.com