-
Notifications
You must be signed in to change notification settings - Fork 41
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
tmux integration #37
Comments
I'm not certain what iTerm2 is doing here, but whenever I read that a terminal has an 'integration,' my first thought is 'layering violation.'
It's conceivable, if this protocol is robust, well-specified, and complete, that notty would implement a client for this protocol, to interact with terminal multiplexers. This would not be a tmux-specific integration, it would be a different way of transmitting commands between notty and the controlling process. There's not enough documentation on tmux's man page (and I haven't found any other documentation yet) for me to tell exactly how this protocol works. The exact implementation in iTerm2, where when you run That said, rather than focusing on the integration with tmux, its worth asking:
Possibly, implementing a client for tmux's protocol is the general purpose answer, but possibly there's something else we could do instead / as well. |
my idea is separation of concerns: instead of providing windows, panes, scrollback, … it could be deferred to tmux. just food for thought, no more. |
My impression of iTerm2's tmux integration (though I haven't used it extensively) is that it runs in the opposite direction: it provides tmux's decoupling ability (so that when you close the window, the tty doesn't die) while using iTerm2's display features. |
yes, that’s what i meant:
|
what iterm2 does is amazing, so let’s do that!
The text was updated successfully, but these errors were encountered: