Towards Trust in Emacs

Emacs, the famously powerful text editor, just got a new peace offering for its trust drama: trust‑manager, a simple add‑on that asks once per project, “Do you trust this?” and then gets out of your way. It even auto‑trusts your own setup and shows a little red “?” you can click to flip a file to trusted. It’s on MELPA, the community package hub.

Cue the comment fireworks. One camp is ecstatic about reducing friction without throwing security overboard. Another camp is torch‑in‑hand mad at Emacs’s whole security vibe. The sharpest diss? A user declared the current trust model “makes no sense” and even “sins against logic and lisp,” arguing it’s paranoid and breaks the flow. Others zoomed in on the absurdities: why does Emacs distrust its own scratchpad? As one lamented, “Why is scratch untrusted!?” People joked that Emacs now has a built‑in trust therapist—and the red “?” is the Scarlet Letter of your code.

Security realists threw confetti at the author’s line that high‑friction safety backfires—“yes, finally someone gets it.” But the broader frustration bubbled up too: a top‑voted gripe begged for real sandboxing so tools stop asking for your whole disk and the internet just to autocomplete. Meanwhile, a tangent exploded about AI‑generated code and how trust is bigger than toggles—if you don’t understand the “why,” you’re not shipping it.

Bottom line: trust‑manager aims to calm the chaos with just‑in‑time prompts, but the community is split between “thank you” and “this system is broken—try again.”