Expand description
CM.2: the host’s answer to a plugin operator that declared a chord.
lattice-plugin-loader learns, at drain time, that a plugin’s operator
wants gc. It cannot bind it: the operator-pending composition — motion
targets, the doubled linewise form, i_ / a_ text-object pendings, the
f / F / t / T find-char pendings — is built from host-resolved
builtin ids, and the loader does not (and should not) depend on
lattice-host.
So the host implements lattice_mode::OperatorChordWirer over
crate::keymap_normal::register_operator_bindings_in and publishes it as
a service. This is the same split N.1.3 made for narrow’s zn, with a
process boundary in the middle: the provider owns the spec and apply, the
host owns the chord wiring.
Structs§
- Host
Operator Chord Wirer - Holds the boot-resolved pieces the composition needs. Cheap to clone; the
id tables are
Copy-ish value types captured once at boot.