cga2000 wrote:
I recently installed vim 7.x and I'm very impressed with all the new
features, especially the new tab stuff ..
On the other hand, I'm sorry to say that there is _ONE_ feature that's
literally driving me _NUTS_.

If I hit the CTRL-P combo by accident .. "p" is very close to "[" ..
and I use CTRL-[ a lot .. well, some "popup menu" materializes out of
the blue ..  presenting me with a list of "completion" choices ..

Thanks, but I am not senile or otherwise mentally challenged  .. I know
what I want to type .. and most of the time vim does not ..  and since I
can type reasonably well .. I do _NOT_ need this completion "feature".

Is there any way I can turn of this completion popup .. ?

Since unwanted popups is one of the absolute evils of the web .. I'm
unsure why this should have become a default feature of the current
version vim and I sincerely hope it will cease to be the default with
the next release.
Maybe this might make some sense for GUI users .. but could it be left
our of the terminal version?

Thanks,
cga



        :imap   <C-P>     <Nop>

will make it do nothing. Another possibility (I think) is

        :set complete=

which should (IIUC) disable both Ctrl-N and Ctrl-P except when the popup is _already_ up.

A third possibility is to disable the +insert_expand feature at compile-time.


BTW, me too I know what I want to type, but I found out recently that for _long_ words which have already been used in the current session (or in any file still listed in the buffer list) it is often more efficient (and less error-prone) to type the first letter(s) then Ctrl-N, then maybe a few additional Ctrl-N's to select the right entry, than to type the whole shebang by hand again. If there are too many completions, Ctrl-P to get back to what I typed then add letters one by one, will usually narrow the choices to just a few, including the one I want.

And yes, I use mostly gvim, but I would use it the same way in Console vim.


As for making it the default in console Vim only, I don't see why a feature which works identically in gvim and console Vim should have different defaults in both, especially when it is easy to disable it in the vimrc.


As for disabling Insert-mode completion by default in both console Vim and gvim, don't count on it: Bram has a long history of preferring whatever doesn't break existing behaviour, and I can't fault him on that. ;-)


Best regards,
Tony.
--
Hackers know all the right MOVs.

Reply via email to