3 ms·
>then I do try it and it turns out it's a pain in the ass to make it work on Windows and I spend more time fiddling with it than I do working with it. The firs
by BeetleB 8y ago
>then I do try it and it turns out it's a pain in the ass to make it work on Windows and I spend more time fiddling with it than I do working with it.
The first few times I did it on Windows it was a pain (almost a decade ago). You had to install some dependencies manually. But the last few times I did it it really was a straightforward install, with everything working out of the box (except any commands that rely on GNU tools like grep). I may have been using an unofficial port - sorry but I don't remember the link.
My Windows Emacs is almost identical to my Linux Emacs. You wouldn't know you're not in Linux. That, for me, is the joy of Emacs - it behaves the same on both OS's.
- tcoff91 8y agoHow did you get magit to not be slow as hell on Windows? It’s brutally slow on my windows box and lightning quick on my Mac.
- Naomarik 8y agoBest setup I've found was to run everything within WSL when developing on Windows and exporting emacs display to Mobaxterm's x-server for a proper emacs experience. Everything is extremely fast and I find myself using my Mac less frequently now since WSL is working very well for me.
- BeetleB 8y ago>How did you get magit to not be slow as hell on Windows? By using mercurial :-) Had no idea magit is slow on Windows. Any idea why?
- nickbarnwell 8y agoIt’s mainly due to the cost of spinning up subproccesses and certain FS operations on Windows. Magit spins up a bunch of git processes for certain operations and can be quite slow due to it. Look into fscache settings for a speedup
- kungtotte 8y agoA plain vim or Emacs is trivial to set up and is indistinguishable, simple config changes are also trivial, but once you go deeper into plugins/layers for things like fuzzy file finders it starts to fall apart because they start relying on Linux-only tools or the Windows equivalent tools aren't as good. Some of it you can get to work after copious amounts of fiddling, but I don't have that kind of time or willpower. While it might not be as powerful the total amount of time I've spent actually making config changes in VSCode is probably about 30 minutes. This is including time waiting for extensions to download! Not to mention that it ships with many features out of the box such as git integration.