1

I'm using the vim ctrlp plugin, and the <c-p> (Ctrl+p) key binding / command (which invokes :CtrlP) often goes back to the vim default of moving the cursor up a line. I can't figure out why this is happening. How can I debug this?

(I've been using the vim ctrlp plugin (https://github.com/ctrlpvim) for 5+ years, and this just started happening in the last month. I've updated the bundle to the latest code from 25 May 2020.)

I thought maybe the mapping was getting lost, but before and after this behavior, the mappings are the same:

:filter /ctrlp/ map
   <C-P>         <Plug>(ctrlp)
n  <Plug>(ctrlp) * :<C-U>CtrlP<CR>

And when it happens, I can still use :CtrlP to get the same functionality as the <c-p> / Ctrl+p command that is no longer working. If I exit vim and start vim again, it works again.

Workarounds:

  • use :CtrlP

  • use Shift+Ctrl+p

  • restart vim

     $ vim --version
     VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Aug 20 2020 22:44:15)
    

Update (31 Aug 2020):

Per user938271's comment below, it looks like this might be either a vim issue or an iTerm2 issue: https://github.com/vim/vim/issues/6794

2
  • 1
    Might be related to this issue: github.com/vim/vim/issues/6794
    – user938271
    Aug 31, 2020 at 15:23
  • 1
    Thanks! I tried shift+ctrl+p when it is in this state, and that indeed works. I added a comment on to that issue. Aug 31, 2020 at 16:18

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Browse other questions tagged or ask your own question.