docs.rs failed to build tear-core-0.1.3
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.
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.
tear-core — runtime logic for the tear multiplexer.
Houses the session/window/pane state machine, PTY ownership
(portable-pty), the layout engine, and the [InProcess]
implementation of [tear_types::MultiplexerControl].
Why this matters for the mado integration
mado currently owns its own pane.rs/tab.rs with private
state machines. At M5 those modules rebase onto
tear-core::InProcess — both apps then share one source of
truth for pane semantics. This crate's InProcess impl is the
gravitational center the eventual rebase lands on.
No daemon — those live in tear-daemon. Daemon-side composition
wraps InProcess rather than reimplementing.