Support keybind-based (instead of ControlClient
-based) actions
#2
Labels
Kind: Enhancement 🔮
New feature or request
Target: Communication protocol 💬⚠️
A part of the core library which deals with client-server messaging
Target: Core 💥
Core architectural support library
Target: Reference implementation 📃
The "official" Client & Server implementations
There are several valid use cases in which the user's shell (inside a session) is not able to communicate directly with the server that is executing said session. The two most important of such are when the user
su
s away (and no longer has write access to the socket) and when the session is running an SSH (or any other remote-ish) connection where the prompt the user can type in no longer has access to the socket. (In the latter case, even access to themonomux
binary might be unreliable.)We should support some rudimentary keybind-based (e.g., screen's or tmux's
C-a
) system where the user can bind a shortcut to a commonly used action.The text was updated successfully, but these errors were encountered: