Describe the bug
In the gvim 8.2, somewhere between patch 567 and patch 775+, something changed that broke ctrl-p's input prompt. User can type any character but underscore "_" somehow is ignored. The last known good one I tried is patch 566.
To Reproduce
Detailed steps to reproduce the behavior:
0. install ctrl-p
gvim from patch 775+Expected behavior
All characters should be echo'ed back on the input line. vim in console mode has no such issue. All versions <= patch 566 are ok.
Screenshots

Here the underscore key moves the cursor up on the "==NO ENTRIES==" line
Environment (please complete the following information):
Included patches: 1-775
Huge version with GTK2 GUI. Features
Ubuntu 16.04
Additional context
Reported also here
ctrlpvim/ctrlp.vim#545
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.![]()
I can't reproduce on Ubuntu 16.04 with GTK2.
I tried like this:
vim -Nu NORC -g --cmd 'set rtp^=/path/to/ctrlp.vim'
" press: C-p _
" result: the underscore is correctly inserted on the plugin's prompt
I guess something else is needed to reproduce? Maybe the plugin needs to be configured in a certain way?
Thanks for the response, I tried the same command above and can still reproduce the problem.
are you using latest from "https://github.com/ctrlpvim/ctrlp.vim" ?
Let me try 960 first. I think the other report on this is on 940.
Yes, I just cloned the plugin with this command in a temporary directory:
$ git clone https://github.com/ctrlpvim/ctrlp.vim
Then I added the path to the plugin in my runtimepath.
The plugin works, because when I press C-p, the prompt is displayed.
Just tried 960, no dice, same result with the command above. What I do notice this is that the issue is not just underscore. Basically somehow all chars like $ ^ are treated like the normal mode - i.e. if I type something in the input line and type "up arrow" to the result list, $ moves the cursor to the end and ^ to the beginning.
Anyway, since you can't reproduce I will just wait to see if more people report this. Thanks again for your time.
That was the gui version? Which one? Can you bisect and find the commit that caused this?
FWIW, here are all the commits whose message contains "GUI", inside the range mentioned in the OP (i.e. from 567 up to 775):
If I could reproduce, the first commit I would check is 8.2.0765.
I can reproduce with 8.2.957, GTK3 GUI, on Ubuntu 20.04 LTS. ctrlp.vim version 1.79.
git bisect tells me fd615a3 (7.0.0765) is the 1st bad commit.
It's probably relevant that _, ^ and $ require me to hold down Shift.
(A few commits are so bad I can't launch ctrlp with Ctrl+P, I have to use :CtrlP. Then Ctrl+P starts working, but _ doesn't.)
For those of you who can reproduce, can you check whether ef6746f helped in any way?
I haven't checked 8.2.1019 specifically, but the current git master (8.2.1034) works fine: I can enter _ and ^ into the ctrlp.vim plugin after launching the GUI with vim -g.
closing then.
Closed #6243.
I noticed that the issue can be fixed by setting g:ctrlp_key_loop=1 to enable multi byte characters.
However, it will take away g:ctrlp_lazy_update from you!!