A note from the beginning.

I kept returning to Neovim and Emacs for different reasons. Neovim was the editor in which I worked most efficiently. Emacs was the editor that most strongly shaped what I thought an editor could be: a living environment, shaped from inside rather than merely configured from outside.

Evil let me keep both, but it also made the seam visible. Documentation and packages assumed one interaction model while I used another, and the small adjustments accumulated. That experience stayed with me: flexibility is not the same as belonging.

Odra draws from Emacs openly. Familiar commands and muscle memory are worth carrying forward when they still work. That influence does not need to be hidden or defended.

I also wanted to build a systems project outside my familiar work, using languages I found enjoyable rather than merely admirable. Odin gave me an ergonomic native foundation. Racket offered a programmable layer in which syntax seems to leave more room for thought. I had wanted a reason to build something substantial with both.

The question became simple: what would an editor shaped by Emacs become with Odin at its core and Racket as its programmable control plane? Once the question appeared, it was difficult to leave unanswered.

Odra will begin with a more Emacs-like interaction model, while reserving space for modal and Vim-like editing from day one. The modal model will come later, but it will not be treated as an add-on or left to a compatibility package. Its exact design is still open. The goal is for both models to feel native to the editor.

Even the name holds more than one small story, both technical and geographical. Odra exists because several long-running curiosities met at the right moment. For now, that is enough.

Odra is at v0.2.0, with recovery checkpoints for unsaved edits. Unexpected hangs can still occur as the editor evolves.