You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Bug #1558: Arrows don't work on console vim

Kind bug
Product Command-T
When Created , updated
Status closed
Reporter anonymous
Tags no tags

Description

This may very well be a bug in my setup, but I'm only seeing this with command-T so I thought I'd mention it here.

I have console vim compiled with Ruby support, and when I use the arrow keys to navigate the command-T dialog, vim enters a single letter and exits command-T. I'm on 64-bit Snow Leopard and this occurs in Terminal.app.

Comments

  1. Greg Hurrell

    This depends on your Terminal settings.

    When you press the arrow keys, depending on your Terminal settings, the Terminal will actually send an escape sequence consisting of several characters.

    See ticket #1531 for more information.

    Seeing as I can't anticipate what different terminal settings different people might use, for version 0.5 I added the ability to set up custom mappings to override the defaults. ie. to set up a mapping which works for you and replaces the existing "down" mapping, you would set a mapping up for g:CommandTSelectNextMap. Look in the help :h command-t-options for a full list of options.

    You might also be able to fix it by making a tweak as described in :help vt100-cursor-keys (as noted in ticket #1531), and not need to set up any custom mappings. Worth a try at least.

  2. anonymous

    Thanks for the reply - I'll look into your suggestions. I neglected to mention in my original post that this happens inside GNU Screen - without screen it works as expected in Terminal.app, just that ESC isn't mapped and I have to use ctrl-C to dismiss the file list, which is OK.

    If I do set my TERM env variable to xterm-color in screen, everything works fine again. Since that doesn't seem to have any adverse affect on other console apps that I use, that's what I've been doing, and happily using Command-T on the console since.

    -Norman Clarke

  3. Greg Hurrell

    Closing due to inactivity.

  4. Greg Hurrell

    Status changed:

    • From: new
    • To: closed
  5. Greg Hurrell

    Marked ticket #1751 as a duplicate of this one.

Add a comment

Comments are now closed for this issue.

Menu