Hi Lifepillar and list, 2016-12-11(Sun) 21:40:07 UTC+9 Lifepillar: > Thanks for the quick reply! I do not think that this is the correct fix, > though. According to the manual (:h i_CTRL-X_CTRL-V), when the pop-up menu > becomes visible after <c-x><c-v>, pressing <c-x><c-v> again behaves like > <c-v> or <c-n>. I'm fine with such behaviour, which is justified in the > manual. The problem is only when <c-x><c-v> returns no matches. Then it > doesn't make much sense to stay in command completion mode.
Ah, You are right. I update a patch. I changed only when <c-x><c-v> returns no matches. Thanks. -- Best regards, Hirohito Higashi (a.k.a. h_east) -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
diff --git a/src/edit.c b/src/edit.c index 0d9e9d4..6003d7b 100644 --- a/src/edit.c +++ b/src/edit.c @@ -2287,7 +2287,7 @@ vim_is_ctrl_x_key(int c) #endif case CTRL_X_CMDLINE: return (c == Ctrl_V || c == Ctrl_Q || c == Ctrl_P || c == Ctrl_N - || c == Ctrl_X); + || (c == Ctrl_X && compl_matches > 0)); #ifdef FEAT_COMPL_FUNC case CTRL_X_FUNCTION: return (c == Ctrl_U || c == Ctrl_P || c == Ctrl_N);
