Self-contained Emacs-like editor written in Chez Scheme runs without installation

The editor presents itself as a Scheme system first and a text editor second. Every component, core, syntax modes, bracket matching, is an R6RS library with a published, immutable API. This design enforces boundaries at the language level: internals are invisible, exports cannot be reassigned, and the core remains stable even as extensions evolve. Engineers who value language-enforced modularity over ad-hoc extension mechanisms may find this approach more maintainable than traditional Emacs Lisp configurations.

Hot-reloading is built into the workflow. Saving a module inside the editor reloads it into the running session; external edits are picked up with `reload-module!`. Registrations are replaced, dependent modules recompile, and buffers remain intact. This eliminates the need for restarting the editor during development, but it also means that stateful extensions must handle reloads gracefully or risk inconsistencies. The editor itself is developed from within itself, suggesting confidence in the reload mechanism’s reliability.

The editor has no dependencies beyond Chez Scheme and a Unix-like terminal. A single checkout runs in place with no build or installation step: the first start compiles the libraries, and subsequent starts take about 100 ms. This self-contained design allows the editor to be vendored inside a project, ensuring that anyone who clones the project gets a working editor with it. Project-specific modules dropped into the vendored checkout’s `lib/` directory remain local to that project, avoiding conflicts with other installations.

Key bindings and commands replicate familiar Emacs workflows, buffers, windows, kill ring, incremental search, without being a direct clone. The editor includes a Scheme top level accessible via `M-x`, with symbol completion, parameter hints, history, and a transcript buffer. Undo reports what it undoes, and typed characters coalesce into runs for cleaner history. While this design simplifies debugging and extension, it also means that engineers accustomed to Emacs’s broader ecosystem of packages may find the feature set limited or require additional Scheme libraries to replicate their workflows.