July 22, 2026
Copy-paste shame sparks a nerd war
Malleable Computing, Emacs, and You
One coder got tired of copy-pasting—and the comments turned it into a philosophy war
TLDR: A developer turned a repetitive copy-paste chore into a custom Emacs workflow using GitHub’s command-line tool, showing how easily some software can be reshaped. In the comments, readers turned that tiny hack into a big argument over whether customizable tools are the future—or just a niche obsession.
A programmer wrote a love letter to making your tools bend to your will after getting sick of manually copying GitHub tasks into Emacs, a famously customizable text editor. Instead of building some giant new app, they stitched together a quick fix using GitHub’s command-line tool, a few converters, and less than 20 lines of code for one key part. In plain English: they found a way to pull online task lists into their personal notes setup without living in a browser all day, and the crowd immediately treated it like far more than a productivity tweak.
That’s where the real fun starts. The comments basically split into “this is the future of computing” and “hang on, there’s a middle ground here”. One fan said Emacs-inspired thinking pushed them to build a whole Lisp system in a web server, which is the kind of sentence that makes outsiders back away slowly while insiders cheer wildly. Another tried to calm things down by arguing that not everyone wants total control—some people just want simple building blocks they can snap together. Then came the broadside hot takes: “JavaScript already did this for the web” and “AutoHotkey is this for Windows,” turning the thread into a mini turf war over which tool really owns the dream of endlessly customizable software.
The funniest running vibe? The author admitting they copied things over manually “like an animal” before automating it. The original poster even jumped into the thread with a cheerful “happy to answer questions,” while everyone else basically used the moment to debate the future of software freedom, personal tooling, and whether nerds secretly just want every app to become their own little kingdom.
Key Points
- •The article documents automating the transfer of GitHub issues into Org Agenda entries in Emacs.
- •The author defined requirements that included working primarily in Emacs, creating and opening GitHub issues, using Org syntax, and avoiding direct authentication handling.
- •The implementation intentionally avoids building a full GitHub client or complex synchronization between local and remote state.
- •The solution uses the GitHub CLI (`gh`) as the interface to GitHub, with Emacs invoking shell commands and parsing JSON responses.
- •The resulting Emacs package, `fj`, includes a function that fetches GitHub issues in fewer than 20 lines of code and displays them in a vtable interface.