5 ms·
> Windows, it took me ages to get a working spacemacs build on it. spacemacs may not be considered as GNU Emacs. spacemacs can often break when any of the depe
by pksadiq 10y ago
> Windows, it took me ages to get a working spacemacs build on it.
spacemacs may not be considered as GNU Emacs. spacemacs can often break when any of the dependency package break.
Also many people who began life with spacemacs usually switch to vanilla emacs + packages later to get more control on what they do.
- vvanders 10y agoSure but getting emacs running was 98% of the pain, spacemacs its self was very straightforward.
- Jtsummers 10y agoI've not used spacemacs, but I use emacs on Windows. What issues have you faced, in particular? I typically just download the latest build from the project itself, uncompress it, and run "runemacs.exe". The hardest part is figuring out where emacs thinks your home directory is (for me it's c:\users\<username>\appdata\roaming) to place your config files in (well, I have a config file there that loads my actual config file in a more sane location).
- vvanders 10y agoThe biggest issue was building emacs. I couldn't find a clear binary distribution that didn't set-off all my malware radar(hello sourceforge!) so getting mingw32 to play nice and build took much more effort than it should have. MinGW/GitBash include Vim by default so there it makes the setup process a no-brainer.
- Jtsummers 10y agohttps://www.gnu.org/software/emacs/download.html https://www.gnu.org/software/emacs/download.html This is where I've gone for my binaries, and I've never had an issue (for windows, on OS X and Linux I just use the appropriate package manager I use for everything else).
- nonsince 10y agoI'm loving spacemacs, but I can already see that I will do exactly this eventually. Evil is fantastic (because vim is fantastic) but I've been a power-user for long enough to have a strong opinion over exactly what I want.