WEB Signal 409
DREI: WYSIWYG Emacs for HTML
↗
Illustration only Photo by Da Nina on Unsplash
DREI is a Tauri-based editor that gives Emacs-style keybindings for WYSIWYG editing of HTML fragments selected by a CSS selector.
Engineers can edit HTML while seeing the final rendered layout, eliminating the need to switch between source and preview windows. The tool retains familiar Emacs motions but lacks undo and incremental search, so it works best when those features are not critical or when supplemented by another editor.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
DREI implements core Emacs editing movements and markup commands for HTML, written in JavaScript inside a Tauri desktop app.
Editing is confined to a node chosen by a CSS selector; changes are saved via a local file write or an HTTP PUT that updates only the selected fragment.
The current alpha version does not provide incremental search or undo, requiring users to fall back to other editors for those functions.
THE READ
What the cluster adds up to.
Before DREI, the author edited blog posts using a Scheme representation, then Org mode with a Pandoc wrapper, and finally manual HTML editing with a minor mode that hid markup. All of these approaches required working with a representation that did not resemble the final rendered page, making it difficult to see CSS effects while editing.
DREI changes this by presenting a live view of the page while allowing Emacs-like commands to modify the underlying HTML. Built as a Tauri application, it exposes a subset of Emacs motions and adds HTML-specific actions such as wrapping regions in tags or inserting lists. The editor can read from a file or a remote URL, and writes back only the portion of the document matched by a supplied CSS selector, letting a server handle boilerplate.
For engineers, the immediate benefit is a WYSIWYG experience that reduces context switching and the need for separate preview tabs. Because the editing commands mirror those of GNU Emacs, users familiar with Emacs can adopt DREI with little retraining. However, the absence of undo and incremental search means that complex refactoring or error-prone editing may still require switching back to a full-featured editor.
The tool’s current limitations confine it to single-page editing and depend on a server to expand or contract the HTML around the editable fragment. As an alpha release, it may contain bugs or missing features that could disrupt workflows if relied upon for critical production tasks. Consequently, DREI is best suited for scenarios like blog authoring or documentation where the server can manage surrounding markup and the editor’s core feature set satisfies the editing needs.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER