ExecutionPolicy
What a call waits and holds when the caller did not say.
Source and package
- Qualified name
-
libtmux::Execution Policy - Namespace
- libtmux
- Package
- libtmux-cxx
- Source
- include/libtmux/command.hpp
-
Description#
A timeout on the call is still how a caller says "this one in particular": listing sessions does not share a deadline with attaching a client. What was missing was a floor. Typed methods passed no timeout at all, so
window.rename(...)waited for as long as the process ran if tmux never answered — and "tmux is normally fast" is not a liveness guarantee when a hook blocks, a filesystem stops answering, or a connection breaks without closing the pipe.Thirty seconds is far past every tmux command that works and far short of forever.
wait_foropts out, because waiting is the whole request.
Members3#
- output_limit: std::
optional <std::size > attribute Absent leaves the transport's own bound, which is one megabyte._t - timeout: std::
optional <std::chrono:: > attribute Absent means wait. That is a thing to mean deliberately.milliseconds - tmux_binary: std::
filesystem:: attribute Which tmux to run.path