Skip to main content

Crate escriba_runtime

Crate escriba_runtime 

Source
Expand description

escriba-runtime — editor state machine.

Wraps everything: BufferSet, ModalState, Keymap, CommandRegistry, Layout. Exposes tick(input) which advances one frame’s worth of state given one input event. Pure — no rendering, no I/O beyond file save/load through BufferSet.

Re-exports§

pub use breakpoint::Breakpoints;
pub use status::PromptKind;
pub use status::StatusModel;

Modules§

breakpoint
Breakpoints — where the operator asked execution to stop.
scan
The scan runner — the courier’s first real carrier.
status
The status line, as DATA — one model, rendered by every face.

Structs§

EditorState
Full editor state — the single Rust value the binary hands to the renderer each frame.
EditorWindow
EditorState read through the counter.
OperatorPending
Re-exported from escriba_mode, which now OWNS the operator-pending FSM.
PluginHost
Holds the editor’s registered lazy plugins and decides which to activate when a trigger fires. The returned entry sources are applied by EditorState (which owns the keymap / command registry / option store).
SemanticPaint
Semantic tokens for one buffer, sealed with the world they describe.

Enums§

LazyTrigger
A lazy-load trigger — the runtime-native projection of escriba_plugin::ActivationTrigger (the binary parses the caixa’s :ativar-em strings and registers these). Startup plugins are applied eagerly by the binary, never registered here.
OpState
Re-exported from escriba_mode, which now OWNS the operator-pending FSM.

Functions§

operand_capture_order
The chain’s order, for the gate in tests/operand_capture_order.rs.