11

I'm trying to use the new iTerm app on my Snow Leopard Mac, but my Ctrl seems to be completely dead (as in non-responsive, as in nothing happens when I type Ctrl+a except for an outputed 'a') and I haven't found anything useful while googling. The closest match was this thread here on stackoverflow, but everything in Terminal.app works as it should.

And, even more strange - I can Ctrl+z myself out of applications, but I can't save files in Emacs (C-x C-s) or any other keyboard shortcuts that uses a Ctrl shortcut. And it's not local, since Ctrl is as broken on my iMac as it is on other unix computers I've sshed onto with iTerm. I've tried both in bash and zsh.

I've tried to remove all files concerning iTerm.app in my ~/Library/Application Support, and I've tried the very latest version (currently 13 h old) of iTerm I could lay my hands on, but to no avail.

Any ideas?

David Medinets
  • 5,160
  • 3
  • 29
  • 42
monotux
  • 3,657
  • 28
  • 30
  • Just a guess: Have you checked `~/.inputrc`? – ofi May 16 '11 at 01:23
  • Just wondering, should this question be tagged with `bash`? – Samveen Jun 05 '12 at 05:35
  • If you run `stty`, what is the output? How does the `stty` output compare to other terminals (e.g. you say it works in Apple's Terminal)? Also check the Preferences, "Keys" pane in iTerm2 because you might need to fix the setting that remaps the Control key to something else. – Kevin Grant Jul 05 '12 at 00:57

2 Answers2

1

This seems to be an iTerm bug.

You can work around it by creating a key mapping in the profile settings. Add a mapping for ^x so it sends 0x18 (which is the encoded form of ctrl+x).

Screenshot

Felix Lange
  • 1,572
  • 11
  • 15
0

I suggest to check this post to see if the ctrl key is enabled in your preferences

https://apple.stackexchange.com/questions/52041/how-to-press-control-key-on-mac

Did you try to configure key bindings for this terminal emulator as specified in the iTerm wiki:

http://code.google.com/p/iterm2/wiki/Keybindings

at last, have you try set -o emacs or set -o vi?

If it works, set it in your ~/.bashrc to run it at login.

Community
  • 1
  • 1
tombolinux
  • 198
  • 6