November 28, 2025
Who moved my socket?!
Don't tug on that, you never know what it might be attached to
From mystery plug to editor meltdown, commenters split between nostalgia and “fail fast” vibes
TLDR: A small mix-up over where a program keeps its “doorbell” caused Emacs to refuse to open files. Commenters argued for clearer, louder error messages, debated tech complexity then vs. now, and called out gatekeeping, while memes kept it fun—important because tiny glitches can waste huge time.
A classic Emacs tale got the internet arguing again: the author’s handy script tried to ring Emacs’ “doorbell” (a small connection file), but the buzzer was hiding in the wrong hallway. One program looked in one temp folder, the other stashed the socket in another—cue chaos. The community lit up with snark, nostalgia, and suggestions. markstos sighed that this was written “10 years ago,” back when “vibe coding sleeper bugs” weren’t haunting devs, while others insisted gremlins have always lived in the walls. adrianmonk pushed a serious fix: make the software fail fast and shout when the temp folder is being quietly changed for security—don’t just silently yank the rug. Meanwhile, kace91 called out the insider tone: the post assumes you know Emacs, Linux tools, and all the acronyms, sparking a mini-debate on gatekeeping versus deep-dive storytelling. For levity, linsomniac dropped a Buckaroo Banzai meme (“wherever you go, there you are”), perfectly summing up debugging vibes. There was even a helpful direct link drop from svat to the original bug hunt, because of course the meta wars matter too. In short: one tiny path mix-up became a big mood about clearer errors, security quirks, and making nerd tales readable to everyone.
Key Points
- •emacsclient began failing with “can’t find socket; have you started the server?” despite starting the Emacs server.
- •strace showed emacsclient searched for the server socket at /mnt/tmp/emacs2017/server, which did not exist.
- •The actual Emacs server socket was found at /tmp/emacs2017/server.
- •The mismatch between emacsclient’s expected socket location and the actual socket location caused the connection failure.
- •The author avoided stracing Emacs due to verbosity and used educated guesses to locate the socket under /tmp.