#VIM SUPERTAB CONTEXT OMNI CODE#
I actually think that both semantic code navigation and on-the-fly semantic code checking are more important than auto completion, but I may be in the minority. I do think it's a useful feature, and personally I'd encourage you to setup semantic completion for your languages if it's practical but YMMV. The most important thing is just to know your language, like your editor, and bang out some code. I don't know about depriving yourself in an important way.
Snippets are rather different, they're just a way to factor out common blocks that you write.
Semantic completion makes it easier to write correct code, omnicomplete makes it easier to write code -). You can grab something that looks right but turns out its completely wrong, and the right thing was something similar that you just haven't already typed somewhere (so omnicomplete doesn't pick it up). It just helps jog your memory or save typing. It has no idea if it makes any sense given the context. Omnicomplete just grabs all identifiers in all open buffers and offers them. That means that generally the options they offer you are actually valid. YCM and semantic based completers (like jedi) actually complete methods based on what type you just entered. That way users could choose their favorite brand of completion engine and their favorite method of invoking the completion list, without one choice locking them for the other. Additionally, a popup window appears with documentation on the particular method that's currently selected. in Insert mode, then press Tab and have all of the options come up. Using a combination of Omni Completion and SuperTab, I'm able to do something like: import random random. Ideally, it would be best if plugins like YCM and deoplete would focus on the actual completion framework&algorithm and leave the completion invocation to plugins like Supertab and AutoComplPop. Scroll down in vim omni completion popup. for completions, but I do miss out the other part of YCM - it's completion engines. With YCM, I don't use it because I like to use CTRL-x. If you like it you can use it, and if you don't you just don't use Supertab - you won't be missing out anything you care about.
Supertab, on the other hand, is a well behaved plugin - the only thing it does is modifying the completion invocation. It's main feature is it's semantic server architecture which allows to write completion engines in Python and run them asynchronically(and, of course, the numerous engines implemented for it), but it also does a second thing - it modifies the way you invoke completion. That's the problem with YCM - it does two things.
0 kommentar(er)
