I'm using tcsh and I'm seeing that some of my custom and some of the default bindkey bindings do not work. Why don't they work?

For example:

I load some default bindings: bindkey -e

I check the default bindings for backward-word bindkey | grep backward-word and see:

"\302"         ->  backward-word
"\342"         ->  backward-word
"^[B"          -> backward-word
"^[b"          -> backward-word

When I try to use backward-word, Alt+Shift+b works just fine, but Alt+b does not work. What gives?

I try to create a new binding for backward-word bindkey "^[u" backward-word, but when I try to use it (Alt+u), it acts like backward-char instead.

  • that new binding works for me on Ubuntu 12.04 with tcsh 6.17.06 (alt+u -> backword one word). What kind of system are you on? Sometimes it helps to make temporary new account with nothing but standard setup to try things out.
    – Anthon
    Jun 10 '13 at 7:37
  • I'm running on Red Hat 5, using Putty or NoMachine NX from Windows 7. I just tried connecting from a different Windows 7 machine and the bindings from the above example work. Seems like something in Windows is intercepting those keys. Jun 10 '13 at 12:34
  • If you press Ctrl+V then Alt+u, what is inserted? What does ESC u do? Jun 10 '13 at 22:18
  • I see ^[OD. ESC u does backward-word -- seems strange. Jun 11 '13 at 0:53

I resolved this issue. I was running a Linux VM on top of Windows 7. Another program in Windows 7 (AutoHotkey) was overriding those key bindings.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.