Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support keybind-based (instead of ControlClient-based) actions #2

Open
whisperity opened this issue Oct 24, 2022 · 1 comment
Open
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

Comments

@whisperity
Copy link
Owner

whisperity commented Oct 24, 2022

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 sus 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 the monomux 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.

@whisperity whisperity added Kind: Enhancement 🔮 New feature or request Target: Core 💥 Core architectural support library Target: Reference implementation 📃 The "official" Client & Server implementations labels Oct 24, 2022
@christianparpart
Copy link

The leader key (e.g. C-a should be configurable, and repeating it should act like passing that one through to the connected application. (just like in tmux). It should be possible to also bind the leader key to arbitrary keys, e.g. \ or <C-m> / <C-space>.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

2 participants