Hacker News Reader

Comment by ubermonkey | Hacker News Reader

Paralleling Linux and MacOS is pretty simple, but the last time I tried to make the same config work properly in Windows it was a nightmare b/c of the path issues.

View on HN

In the past when I've seen someone extolling Windows/Linux compatibility for something as complex as a detailed Emacs setup, they were using WSL or one of the wrappers like Cygwin rather than native Windows compiles of the tooling.

For whatever it's worth, I've always only ever used the native Windows build of Emacs, and I've never had any awful problems sharing my config between Windows, Linux and macOS. I'm sure I had to expend at least a bit of effort to make this work initially, but it wasn't enough for the process to stick in my mind, and the ongoing effort doesn't feel like it's added up to much.

(I admit it's added up to more than zero though! Keeping (require 'cmake-mode) working reliably on Windows and macOS has proven a minor annoyance, and fonts seem to require a degree of system-specific attention.)

The problem is the dependencies, getting hunspell installed and finding the dictionary files for example. I normally only get a new computer every few years and each time stuff like that is a new pain. And dont even start with treesitter, i cant compile anything on windows and always end up using prebuild dlls.

Are you using Cygwin? That's what I've used on Windows since it was available.

Nope, straight edge windows user.

I have some conditionalization for windows, but not that much. While I haven't used Windows as a daily driver since Windows 8, I have to use Windows for to maintain a port on Windows, and I use Emacs there and it's fine.

Reply on news.ycombinator.com