Reference

The docs site gives orientation and workflow examples. It deliberately avoids duplicating every method, enum variant, and error case. For item-level reference, use generated rustdoc for the crate you are calling:

• tastty-core for parser, screen, encoder, frame, host-profile, and host-reply APIs.
• tastty for PTY session lifecycle, input delivery, snapshots, resizing, and widget integration.
• tastty-driver for builder, session, wait, snapshot, inspect, input parsing, observer, and signal APIs.

Start at the crate root. The crate-level docs describe the intended flow; the type and method pages carry the exact signatures, feature gates, errors, and non-exhaustive markers.

The examples here are intentionally compact. Treat them as orientation for the first few calls, not as complete applications or exhaustive API coverage.