I went through the install process on windows. First it said I need to install gvim first. So I did that. then set the path to gvim.exe Then I was able to install it, and it said just start gvim and plugins will install automatically. So I start gvim and nothing happens. Looks like normal gvim. I feel like these sorts of experiences are always what happen when using kinda linuxy tools. Compare to installing vscode wh…
Show HN: SpaceVim Release v1.5.0
21–25 of 25 posts
Re: Show HN: SpaceVim Release v1.5.0
#22Interesting. So, clearly modeled very closely after Spacemacs. Why would someone use this over Spacemacs in vi mode? (I’m sure there are reasons, just curious what they are)
Re: Show HN: SpaceVim Release v1.5.0
#23I went through the install process on windows. First it said I need to install gvim first. So I did that. then set the path to gvim.exe Then I was able to install it, and it said just start gvim and plugins will install automatically. So I start gvim and nothing happens. Looks like normal gvim. I feel like these sorts of experiences are always what happen when using kinda linuxy tools. Compare to installing vscode wh…
Spacevim is not an editor, that would be vim/gvim, which works fine as you said yourself. Spacevim is a collection of configurations, basically a plugin, and those are working on VS Code as good or bad as on any other editor.
Re: Show HN: SpaceVim Release v1.5.0
#24Interesting. So, clearly modeled very closely after Spacemacs. Why would someone use this over Spacemacs in vi mode? (I’m sure there are reasons, just curious what they are)
Re: Show HN: SpaceVim Release v1.5.0
#25Interesting. So, clearly modeled very closely after Spacemacs. Why would someone use this over Spacemacs in vi mode? (I’m sure there are reasons, just curious what they are)
While Evil mode is good, it is not true vim. That could be one particularly strong reason. There is also performance, emacs is slower than vim, unless you set up an emacs daemon at startup.