Not able to use “compose” key in iTerm2
- iTerm2 Build 2.9.20150523-nightly
- OS X 10.10.3 (14D136)
- com.googlecode.iterm2.plist
- debuglog.txt
I'm using the U.S. custom Keyboard Layout to get a compose key in OS X. This works great everywhere but in iTerm2 (including in Terminal.app). I use the right option key as my compose key, and it is mapped to send Shift+Ctrl+F13 with Karabiner.
In all apps but iTerm, when I press my compose key, a yellow ‘⎄’ character is inserted, and not until a compose sequence is completed is a character actually inserted. So to create the degree sign (°) I send Shift+Ctrl+F13, ‘o’, ‘o’.
In iTerm2, pressing the compose key (thus sending Shift+Ctrl+F13) results in “;2P” being inserted when in emacs mode (set -o emacs) and in vi mode (set -o vi), it leaves insert mode.
The attached debug log is a recording of pressing compose (Shift+Ctrl+F13), o, o in emacs mode. The result is ;2Poo, where the expected result would be a degree sign: °.
If I run vim and ask it to insert the terminal code (ctrl-v in insert mode), it inserts “<F13>” in iTerm2, while in Terminal.app, vim doesn't get anything before the compose sequence is completed (i.e. it is still waiting after I press the compose key).
I have tried to tweak iTerm2 settings without success, and have not found any good ways to debug this as I'm not really familiar with OS X's text input system.
Perhaps iTerm2 is asking the system for “raw” input in some way?