Reattach to a tmux ssh session damages umlaut input

Thanks for filing an issue! Please answer the questions below so I can help you.

• iTerm2 version: Build 3.0.15
• OS version: 10.12.6
• Attach ~/Library/Preferences/com.googlecode.iterm2.plist here (drag-drop from finder into this window)
• Attach a debug log, if possible. Instructions at https://iterm2.com/debuglog

debuglog.txt

• Are you reporting a performance issue or a hang? Please attach a sample. Instructions at https://gitlab.com/gnachman/iterm2/wikis/HowToSample
• Are you reporting a crash? Please attach the crash log. Instructions at https://gitlab.com/gnachman/iterm2/wikis/crash-logs

Detailed steps to reproduce the problem:

1. Start a new ssh session with tmux into my vagrant box with vagrant ssh -c "tmux -CC new-session -A -s main"
2. Press <esc> to detach cleanly
3. Reattach to it with the same command

What happened:

After step 1 I can enter umlauts without any problems, but after step 3 the umlaut entry is damaged and I can't enter äöü anymore.

What should have happened:

Reattaching to tmux sessions should continue to have working umlauts.

It looks like we were sending the right thing. If you attach to tmux without -CC and give it the command send-keys 0xf6 (by pressing ^B first, and then entering that command), do you get an ö?

If I connect using vagrant ssh -c "tmux new-session -A -s main" I am able to enter ö and see it. When entering send-keys 0xf6 I am getting a ?.

This smells like a tmux bug to me. I need to investigate this some more.

changed milestone to %Next Beta

If there is anything I can do to help you with this, just say so.

What version of tmux are you on? Have you tried the latest version?

Sorry that it took me so long. I now updated the version debian included (2.1) to the latest 2.5. Had to compile it myself. And now it works. So this was a tmux bug. Sorry. Will close this now.

closed