EmacsNews

This Week in Emacs

Packages & Tools: The package management conversation resurfaced this week with a Reddit thread comparing package-vc, elpaca, and straight.el. It's a perennially useful discussion for anyone setting up a fresh config — package-vc has matured considerably as a built-in option, and the thread gives a clear picture of where each tool fits. On a related note, another thread tackled which directory variables Emacs uses for plugin data beyond user-emacs-directory — a surprisingly under-documented area that matters when you want a clean, version-control-friendly setup. Doom users hitting doom-sync errors on Emacs 31 got some community troubleshooting this week — a reminder that Emacs 31's arrival is actively shaking things loose in the distribution ecosystem.

On the automation front, buffer-guardian.el hit version 1.0.2, a small package that handles automatic buffer saving — worth a look if you've ever lost work after a crash or accidental close. For Eglot users working in LaTeX, a Stack Exchange thread addressed how to disable specific Eglot keybindings in LaTeX-mode — the kind of targeted configuration question that affects many people writing in mixed LaTeX/LSP environments.

Org Mode: Two developments in the org-roam space stand out this week. The org-roam-tree package received a notable update bringing just-in-time rendering and arbitrary search — a meaningful improvement for anyone with a large Roam database who has felt the performance pinch when navigating their notes. Separately, someone shared a setup for inline backlinks in org-roam, which renders backlink information directly within the note rather than in a separate buffer — keeping context visible without requiring a context switch.

There's also a bug worth knowing about: Org mode has stopped rendering correctly on GitHub in both Firefox and Chromium-based browsers. If you share .org files via GitHub and have noticed broken rendering, this thread is worth checking — it appears to be a GitHub-side issue rather than an Org problem.

For mobile Org users, a thread explored using GNU Emacs and Org-mode to log repeated activities on Android — a practical question with useful pointers toward Termux-based setups and syncing strategies.

Irreal revisited Remember mode, the built-in capture system that predates org-capture, prompted by a Reddit thread where someone discovered it as a kind of persistent scratch buffer. It's one of those built-in features that's easy to overlook entirely.

Configuration & Workflows: Helheim-Emacs landed on Hacker News this week — a new distribution positioning itself as the Helix-inspired counterpart to what Spacemacs and Doom are for Vim users. It's early days, but it signals continued appetite for opinionated, modal-editing-friendly Emacs distributions. On the vanilla side, a well-received Reddit thread collected interesting and underrated vanilla Emacs features — worth browsing even for experienced users. Someone also shared how Emacs now serves as their rofi replacement for application launching and quick actions, using completing-read-based interfaces to handle what was previously a separate tool.

Getting Outlook calendars into Emacs was addressed both on Reddit and by Irreal, who surveyed the current options — relevant for anyone in a corporate environment where Outlook is mandatory but who wants agenda data in org-mode.

Development & Elisp: Two technically interesting projects this week. excali-mode brings Excalidraw — the freehand diagramming tool — running natively inside Emacs. For anyone doing technical writing, architecture diagrams, or visual note-taking, this is worth watching. Alongside it, canvas-browser demonstrates a Chromium page rendered inside an Emacs buffer using the new canvas image capabilities in Emacs 32 — more a proof-of-concept than a daily driver, but a striking demonstration of what the canvas API makes possible.

Someone also built a WhatsApp client for Emacs without an official API — exactly the kind of ambitious project the Emacs community produces regularly. The write-up explains the approach in detail and is worth reading for the engineering alone. Meanwhile, OHEmacs brings GNU Emacs to OpenHarmony and HarmonyOS, expanding Emacs's platform reach in an unexpected direction.

Irreal also noted the Copy Only What You See technique, and covered a Quick Look integration for Emacs — both small quality-of-life items worth filing away.

Community & News: Protesilaos Stavrou has been actively developing a caching layer for Denote — the denote-data cache, which he first announced as an experiment and then gave a status update on this week. The cache is aimed at improving performance when working with large collections of Denote files, and Prot has been sharing his thinking openly as the design evolves. He also published a thoughtful post on Emacs, AI contributions, and the politics of copyright and appeared live on the Root Access stream. The Emacs ATX meetup also took place this week — good to see in-person gatherings continuing.

Deep Dive

The AI Question Comes to a Head

The most significant undercurrent this week is the question of AI — not just as a tool, but as a genuine political and philosophical flashpoint for the community. Three separate threads converged on this: a Reddit discussion on LLM packages in ELPA and the SaaSS problem, another on whether Emacs can maintain its rejection of AI-generated code, and Prot's longer essay on AI contributions and copyright politics.

The ELPA/SaaSS thread surfaces the tension between the GNU project's longstanding position on Software as a Service Substitutes — proprietary services that replace software you could run yourself — and the practical reality that LLM-backed tools are becoming central to many developers' workflows. Whether ELPA should host packages that connect to proprietary AI services touches the core of what GNU software is meant to represent. This is a familiar ideological tension in the GNU project, but LLMs have brought it into sharp relief.

What's notable is how thoughtfully the community is engaging with this rather than simply polarising. Prot's piece in particular is worth reading in full — it carefully separates the copyright question (AI-generated code and FSF copyright assignment requirements) from the broader question of what Emacs should endorse or facilitate. These are genuinely hard problems without clean answers, and the Emacs community is working through them in public.

Denote's Cache and the Maturing of Personal Knowledge Tools

Prot's ongoing work on denote-data caching reflects something encouraging: a package author iterating openly on a significant architectural change before shipping it. Denote has always been committed to simplicity and plain files, so adding a cache layer is a meaningful design decision — it risks introducing hidden state that plain-text advocates rightly distrust. The fact that Prot is sharing his reasoning and progress incrementally reflects the kind of careful stewardship that makes Denote trustworthy. Combined with the org-roam-tree performance improvements and inline backlinks work happening in parallel, this week suggests the personal knowledge management space in Emacs is getting noticeably faster and more capable without abandoning its plain-text foundations.

The Platform Expansion Continues

Both OHEmacs for HarmonyOS and the Android usage questions point to something real: Emacs is reaching platforms that would have seemed unlikely a few years ago. The canvas-browser and excali-mode experiments push at what an Emacs buffer can contain. The Emacs in MicroVM write-up and the WhatsApp client reflect an ecosystem that continues to surprise — not by becoming something it isn't, but by its users refusing to accept limits on what their editor can reach. The Hacker News thread asking whether people keep Emacs installed out of nostalgia offers a useful outside perspective: from a distance, Emacs can look like legacy software. From the inside, it looks like a week like this one.