Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
escriba-plugin — caixa-native plugin model for escriba.
An escriba plugin IS a caixa. A plugin is a directory (a git
repo with a caixa.lisp at its root — the pleme-io git-as-registry
model) whose escriba entry is tatara-lisp declaring the plugin's
keybinds / commands / options / highlights via escriba-lisp
def-forms (and, later, imperative setup via escriba-vm). The
user's rc DECLARES a plugin; escriba RESOLVES it to a plugin
directory, LOADS its entry, and ACTIVATES it (applies the entry's
def-forms to live EditorState) either eagerly or when an
activation trigger fires.
Lineage-safe by design. escriba reads the plugin's tatara-lisp
with its OWN (pleme-io/tatara-lisp) parser; it deliberately does
NOT depend on caixa-core (which is on the other tatara-lisp
lineage) — that would re-introduce a two-lineage conflict. Plugin
install/resolve uses the caixa git model (feira / git) out of
band; this crate is the consumer side: discovery, load, and
trigger-gated activation.