LibTmux.Mcp.WaitOutcome
.NET
- Python Unavailable
- Ruby Unavailable
- Lua Unavailable
- TypeScript Unavailable
- Rust Unavailable
- Go Unavailable
- Java Unavailable
- .NET
- C++ Unavailable
- Swift Unavailable
-
How a wait ended.
Members
-
One of the patterns the caller asked for appeared.
-
The pane printed something, and the caller asked for any output.
-
One of the caller's stop patterns appeared, so waiting was pointless.
-
The time ran out before anything matched.
-
The pane's program exited while the wait was running.
-
A wanted pattern was already on screen when the wait began, and nothing new arrived before time ran out.
This is what a plain
Timeoutwould otherwise report here, with the returned tail visibly containing the very text the wait says it never found: only output arriving after the call counts as new, by design, so calling this right after the command that produced the text - the first thing most callers try - would time out holding a tail that contradicts it.MatchedPatternnames what was already there.