-
Notifications
You must be signed in to change notification settings - Fork 623
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
Feature: Support for tmux's Control Mode #1935
Comments
Ah yes, I've been meaning to do this. I've started working on at least the tmux control mode parser. I believe I'll bring that in via a PR first before integrating more parts of Ghostty into it. Here is a list of TODOs that I plan on doing independently so we don't have one massive PR. The checklist today doesn't necessarily map 1:1 to a PR but is the set of somewhat separable work to do:
|
Nice!! I think it'll also need #189 to really make sense. |
I got the control mode notification parser in in #1946. This is just one of many steps (see my first comment). |
Is this the same as the tmux integration in iTerm2 (enabled by adding If so, consider this a gigantic +1 (+1M). I'm so dependent on that feature that I'll probably continue to use iTerm2 until Ghostty or another terminal emulator supports it. |
@dtenenba Yes, an equivalent feature implemented in Ghostty is the intended outcome from this issue. |
Sorry is this also the same as 'programmatic control' so that Vim-Tmux-Navigator works simultaneous on Nvim and a tux terminal pane? |
tmux has a feature called Control Mode, which allows a client i.e a terminal emulator such as Ghostty to manage tmux panes. This has the benefit of enabling native integration with the terminal emulator and by extension the host OS system, making it easier to manage buffers without having to jump through hoops imposed when using tmux directly.
The text was updated successfully, but these errors were encountered: