Crate osc7501 

osc7501-rs

Tell your terminal when your program is working, needs input, or has finished. This crate sends OSC 7501 revision 0.4 reports through your existing output writer. A supporting terminal decides how to display them.

Send a status

[dependencies]
osc7501 = { package = "osc7501-rs", version = "0.1" }

use osc7501::{AppId, Kind, State, Status};
use std::io::Write;

fn main() -> Result<(), osc7501::Error> {
    let mut output = std::io::stdout().lock();
    Status::new(State::Blocked)
        .app(AppId::new("my-tui")?)
        .kind(Kind::Permission)
        .message("Apply these changes?")
        .write_to(&mut output)?;
    output.flush()?;
    Ok(())
}

In a TUI, use the same writer as your screen rendering to keep writes in order. You control flushing. Validation and encoding finish before writing starts; an I/O error can still leave a partial frame.

Update or clear a status

• Each report replaces all fields of its record. Repeat fields you want to keep.
• A report without an id describes the whole program. Use RecordId::new and .id(id) for child tasks such as build/test.
• Use Progress::new for percentages from 0 to 100 on working or blocked reports. Omit progress when the amount of work is unknown.
• A blocking kind applies only to blocked. Send idle after cancellation, or done or error when work ends.
• Status::clear().id(id) removes that task and its children. Status::clear() removes every record.

Reuse report metadata

Use Context when several reports share an app, record id, or title:

use osc7501::{AppId, Context, Progress, RecordId, State};
use std::io::Write;

fn build(output: &mut dyn Write) -> Result<(), osc7501::Error> {
    let task = Context::new()
        .app(AppId::new("cargo")?)
        .id(RecordId::new("build/tests")?)
        .title("Test suite");

    task.status(State::Working)
        .progress(Progress::new(25)?)
        .message("Running tests")
        .write_to(output)?;
    task.status(State::Done).write_to(output)?;
    output.flush()?;
    Ok(())
}

Each status(state) starts a fresh report with the context’s app, id, and title. The done report above has no message, progress, or blocking kind. Set those fields explicitly on each report that needs them. Reports still replace all fields in the terminal’s record.

A context borrows its fields and allocates nothing. It holds no writer or current status. Report setters can override the repeated fields without changing the context. Title validation still happens in Status::write_to. Omit .app(...) for child records that should inherit their app from an ancestor.

Reply from a terminal host

Use CapabilityReply with the writer that sends input to the program. Advertise only what your host implements:

use osc7501::{CapabilityReply, State};
use std::io::Write;

fn answer_query(output: &mut dyn Write) -> Result<(), osc7501::Error> {
    CapabilityReply::new()
        .states(&[State::Idle, State::Working, State::Done, State::Error])
        .kinds(&[])
        .write_to(output)
}

Omitted lists use the revision 0.4 defaults. Empty lists advertise no support. Replies follow the same writing rules as reports and must fit within 4096 bytes.

A default reply has the same bytes as write_query; both parse as parser::Event::Query. Use stream direction and pending-query state to tell them apart.

Parse and keep reports

osc7501::parser exposes the parser. Add features = ["store"] to the dependency above to also use osc7501::store. Use features = ["store-alloc"] to also enable owned storage with Store::new(capacity). The store guide shows how to keep records and handle terminal cleanup.

The parser and store also work as separate dependencies without std.

Try it

From a repository checkout, run the interactive release playground:

cargo run -p osc7501-rs --example tui

Press s to start and q to quit. The screen shows task progress, reports, and the builder calls that produce them. Use a terminal of at least 80 columns and 24 rows; protocol support is optional.

See the repository README for the host and text demos, or the API documentation for the full interface.

Re-exports

pub use osc7501_parser as parser;

pub use osc7501_store as store;

Structs

AppId

A validated stable application identifier.

CapabilityReply

A terminal host’s capability reply, with borrowed state and kind lists.

Context

Borrowed fields to repeat in each report for a record.

Progress

A validated percentage in the inclusive range 0..=100.

RecordId

A validated hierarchical identifier. Root is represented by None.

Status

Plain-text report to encode. None means absent, not “keep prior value”.

Enums

Error

Validation, parsing, or transport failure.

Kind

Why a blocked record needs the user.

State

A record’s state. Clearing is represented separately by Action::Clear.

Functions

write_query

Writes an optional feature query without reading input or imposing a timeout. This function does not flush the writer.