New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 731251 link

Starred by 4 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Feature



Sign in to add a comment

hterm: support tmux Control Mode

Project Member Reported by marinheiro@google.com, Jun 8 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Steps to reproduce the problem:
Run tmux on a Chrome Secure Shell session.

What is the expected behavior?
Using tmux with the -C (or -CC) flag should start tmux using native windows and panes using the Control Mode.

What went wrong?
Not only it does not work but it also hangs the terminal.

WebStore page: https://chrome.google.com/webstore/detail/secure-shell/pnhechapfaindjhompbnflcldabbghjo

Did this work before? N/A 

Chrome version: 58.0.3029.110  Channel: n/a
OS Version: OS X 10.12.5
Flash Version: 

This feature is implemented successfully in iTerm2. It works really well even on remote sessions on Linux hosts. Unfortunately iTerm2 is only available on OSX and because of that using it is not always an option.

There is some documentation about that in [1].

[1]: http://man7.org/linux/man-pages/man1/tmux.1.html#CONTROL_MODE
 

Comment 1 Deleted

Comment 2 Deleted

Comment 3 Deleted

Comment 4 Deleted

Cc: vapier@chromium.org raymes@chromium.org
I think this would be a super helpful feature. iTerm2 is one of the reasons I've stayed with macOS instead of ChromeOS as more of Google has been moving over.

There's some more background on control mode, including a work-in-progress implementation, on this bug for the Terminator terminal emulator for Linux: https://bugs.launchpad.net/terminator/+bug/1301605

Sign in to add a comment