Rune

R ust UN der E macs

This project is an experimental Emacs core written in Rust. The project is still at a very early phase but has the following goals:

Bring multi-threaded elisp to Emacs
Be “bug-compatible” with existing Emacs Lisp packages (everything should still work)
Enable performance improvements (including faster GC, regex, and JSON) by leveraging the Rust Ecosystem.

See the design doc for more details.

Status

The current goal of this project is to create an editor MVP. We have a basic elisp runtime, and we are working on adding basic editing functionality in a minimal GUI. This will include:

buffer
text insertion/deletion
cursor
line wrapping
scrolling
file IO
display tables

If you want to contribute or have ideas for things to add, please open an issue.

lisp

Lisp files are currently pulled from

https://github.com/emacs-mirror/emacs/tree/emacs-29.1/lisp

Any modification for bootstrapping contain the tag RUNE-BOOTSTRAP.

Running

The easiest way to run the interpreter is with cargo run --profile=release. Running with the load argument (-- --load) will load the bootstrapped elisp and then exit. Running with the repl argument (-- --repl) will open an elisp repl. Running with both arguments (-- --load --repl) will load the elisp and then open the repl. Running with no arguments is equivalent to --load.

MIRI

Run the test suite with MIRI

MIRIFLAGS='-Zmiri-strict-provenance -Zmiri-ignore-leaks' cargo +nightly miri test

Exploring this repo

The project is defined by a main package rune, which depends on the crates included in the crates directory. One of those is the rune-macros crate, which defines the defun proc macro for defining builtin functions. The rest of the code is contained in src/. The modules are described below.

objects: The basic objects used in the interpreter. These are modeled after Emacs objects using tagged pointers with inline fixnums. Conversion between different primitives and object types is also found here.
reader: The emacs lisp reader that translates a string to a cons cell. Due to the simple nature of lisp syntax, the reader is hand rolled and does not rely on any parsing libraries.
env: The global obarray. Currently, function bindings are global and immutable and value bindings are thread-local and mutable. When the ability is added to share data between threads, this will enable new threads to safely run functions without the need to copy them.
gc: Contains the allocator and garbage collector. All code for rooting and managing objects lives here as well.
bytecode: The bytecode VM. This uses the same opcodes as Emacs and uses the bytecomp.el to compile.
interpreter: The basic elisp interpreter. This is used only to bootstrap the elisp byte-compiler.
fns, data, alloc: These modules contain definitions of builtin in functions. Some of these are just stubbed out until the functionality is actually needed.

Contributing

See the architecture doc for more info on the structure of Rust Emacs internals.

This project is moved forward by trying to load new elisp files and seeing what breaks. The best way to do that is with cargo run, which will load the currently bootstrapped files. The bootstrapped files are located in main.rs as part of the load function.

Usually what is needed is to implement more primitive functions. This is done with the defun macro. For example, if we wanted to implement the substring function, we would first look at the lisp signature.

(substring STRING &optional FROM TO)

Then we would translate the types to their Rust equivalent. If the correct type is not known we can use Object. In this example we would write our Rust signature as follows:

#[defun]
fn substring(string: &str, from: Option<i64>, to: Option<i64>) -> String {...}

If you run with cargo run -- --load --repl that will load the current bootstrapped files and then open the REPL. From there you can run (load "/path/to/elisp/file.el") to try loading a new file. Files that are not bootstrapped are not yet included in this repo, but are part of Emacs. Once the file is bootstrapped it can be added to the lisp directory.

Blog posts

tagged pointers in Rust: My initial approach to creating tagged pointers in Rust. It serves as in intro to this project.
implementing a safe garbage collector: An overview of the garbage collector used in this project and how Rust enables safe GC abstractions.

A vision of a multi-threaded Emacs :: Some ideas about how to add multi-threading to the existing language.

Design of Emacs in Rust: Some of the unique benefits that Rust could bring to Emacs.

Further exploration

Remacs: The original Rust and Emacs project. Remacs took the approach of enabling interop between Emacs C core and Rust, enabling them to replace parts of Emacs piecemeal. The project is currently unmaintained but is a big inspiration for Rune.
emacs-ng: The spiritual successor to remacs. This project integrates the Deno runtime into emacs, allowing you to write extensions in elisp or javascript. Which sounds cool if you happen to be a web developer. It really shows the power of integrating Emacs with a more modern ecosystem (which is part of the promise of Rust).
helix: A fast modern text editor written in Rust.
crafting interpreters: This was a big inspiration for this project, and it’s probably one of the best introductions to programming language implementations.

zbelial/rune