Server.over_control
A Server whose commands travel over held-open control clients attached to session(), rather than one launched process each.
Source and package
- Qualified name
-
libtmux::Server:: over _control - Namespace
- libtmux
- Declared in
Server- Package
- libtmux-cxx
- Source
- include/libtmux/server.hpp
- [[
C++ nodiscard attributeAsks the compiler to warn when a result is discarded. An explicit cast to void acknowledges that the result is intentionally ignored.]] expected<Server, ProtocolError > over_control(std::string session, std::_view size connections = 1) const;_t -
Description#
Only where that gives the same answer. tmux can end a command's guarded block before the command has finished, so a command goes over the wire only if the typed surface issues it and tmux cannot defer it as sent —
split-windowwithout-Ior-W,display-messagewithout-I, the listings, and the other commands in the list inserver.cpp, each checked against tmux'sCMD_RETURN_WAIT. Anything else launches, as it would from this Server: a deferring command, one that acts on the client itself, an alias or an abbreviation this cannot see through. A failure reads as the sameCommandFailurea launch would give.connectionsspreads commands over that many clients. One is enough for most callers — a connection already carries concurrent requests — and each extra client is attached tosession()and shows inclients().A command with no target resolves against the control client's session rather than the most recently used one. The typed surface always names a target; a caller passing raw commands through
run()should too.- Parameters