SpaceVim – Like Spacemacs, but for Vim
spacevim.org
SpaceVim – Like Spacemacs, but for Vim
1–10 of 186 posts
Re: SpaceVim – Like Spacemacs, but for Vim
#2… and people wonder why I dislike Markdown. (There are fairly radical rendering differences between the GitHub page and the spacevim.org page, because different Markdown renderers with different bugs have been used, and the Markdown was fairly sloppily written.)
Re: SpaceVim – Like Spacemacs, but for Vim
#3No. Spacevim makes vim works _differently_.
Re: SpaceVim – Like Spacemacs, but for Vim
#4No. Spacevim makes vim works _differently_.
To be fair that's the submitter's title, it's not from the SpaceVim site.
Re: SpaceVim – Like Spacemacs, but for Vim
#5Can't get it to work properly, it seems to be very buggy currently or cerain instructions are missing.
Re: SpaceVim – Like Spacemacs, but for Vim
#6Re: SpaceVim – Like Spacemacs, but for Vim
#7Ok, but what it is? The page doesn't explain it. The top page explanation refers to spacemacs and most vim users don't know spacemacs.
Is it a vim plus a bundle of plugins?
EDIT: Cleaned up the spacemacs sentence.
Re: SpaceVim – Like Spacemacs, but for Vim
#8The greatest dev timesaving tip that someone gave me was to clear my .vimrc and start off with a blank slate. vim is a language in itself [1] and it's easy to try to mimic someone who has conversational fluency in it, but as with languages, the only way to learn in practice from the start. Projects like SpaceVim try to create an IDE like environment, but because of being terminal driven, it's difficult for anyone to "discover" features. You end up with a large distribution with barely used features. Instead by growing and maintaining your own vimrc, you get something that can be both used everywhere (dotfiles and Github FTW) and work FOR you. At the end of the day, vim is JUST another tool to make you work more efficiently.
Trust me. "truncate -s 0 ~/.vimrc" and take the time to learn. You won't regret it in the long run.
Re: SpaceVim – Like Spacemacs, but for Vim
#9… and people wonder why I dislike Markdown. (There are fairly radical rendering differences between the GitHub page and the spacevim.org page, because different Markdown renderers with different bugs have been used, and the Markdown was fairly sloppily written.)
Is there a linter yet for markdown?
Re: SpaceVim – Like Spacemacs, but for Vim
#10I started using Spacemacs recently for its out-of-the-box IDE-like features but the layers' functionality seems to be fairly hit-or-miss and overall the impression is one of a bug-infested nightmare. Every time I try to set up my environment on a new machine, I get some new set of problems that I have no idea how to solve (disappearing powerline, broken neotree, weird projectile caching behavior totally breaking my workflow, busted syntax checking, and more). I don't blame the Spacemacs folks for this; I actually think what they've done is really cool. Emacs simply is what it is, I think. I don't have time nor inclination to learn elisp and build/fix my own environment.
When it does work, it's great. But the inconsistency is probably going to drive me away, back to Vim. I think that if anyone can build a similar thing for Vim that actually works, I'll use it in a heartbeat.