e: A self-aware Emacs-like editor written in Chez Scheme
e is a customizable self-aware Emacs-like editor written in Chez Scheme
e is a tiny console text editor written in Chez Scheme that captures the spirit of Emacs—buffers, windows, a kill ring, incremental search, and a Scheme top level—without becoming a clone. It's built as a Scheme system: a minimal core with an immutable API, extension modules, and hot-reloading. M-x evaluates Scheme against the live editor, with completion and parameter hints. Undo reports what it undoes, and the editor is developed from inside itself. No dependencies beyond Chez Scheme and a Unix-like terminal; it runs in place with no build step.
The editor is a Scheme system: a minimal core with a published, immutable API, and extension modules built on it, enforcing its boundaries with the language rather than with discipline.
- rich_sasha
What is meant to be the selling point over Emacs? Apart from scheme>elisp?
Arguably 80% of the emacs goodness is the terabytes of elisp written in the last few decades, if you break compatibility with that you need to throw in something pretty compelling.
- tommyage
Chapter 12.2, Guideline 1: https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1...
Program names should be between 2 and 9 characters; As a thing to consider. Also, searching for `e` may be weird.
- noufalibrahim
On my machine, e is just a way to send things into Emacs.
$ which e
e () {
snippet="(nkv-find-file-and-jump \"$1\")"
emacsclient --no-wait -e $snippet
}