4

I recently installed vim7.3 using "--with-features=big", because I like almost all of those features. However, one thing that it does that I don't like is enables tab-completion: in normal mode, if you hit tab, vim "intelligently" begins omni-completion if you're near a "word".

Now, I use the Smart Tabs plugin, and I need my tab key to not be auto-complete. However, I like all the other "--with-features=big" features, and I'm loathe to go down to "--with-features=normal", which doesn't affect my tab key.

Does anyone know how to disable the tab-completion when compiling vim --with-features=huge?

  • 3
    In normal mode, <tab> jumps to the next newer entry in the jump list. This behavior is not affected by any Vim feature. In insert mode, <tab> inserts a <tab> character. If you are seeing a different behavior, it is caused by your ~/.vimrc or a plugin. To find out where <tab> is being mapped, execute :verbose nmap <tab>. – garyjohn Oct 4 '10 at 16:54
  • If you had posted that as an answer, I'd mark this question as answered. Thanks for the tip! – So8res Oct 4 '10 at 21:49
3

[Copied from my comment.]

In normal mode, <tab> jumps to the next newer entry in the jump list. This behavior is not affected by any Vim feature. In insert mode, <tab> inserts a <tab> character. If you are seeing a different behavior, it is caused by your ~/.vimrc or a plugin. To find out where <tab> is being mapped, execute

:verbose nmap <tab>
5

you can try this command to find out what has mapped the tab-key in insert mode:

:verbose imap <tab>

and you can get the hint to handle the problem.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.