> That means, vim is expecting a second <Ctrl-> Letter, to choose the
> completion you want. There are several different ways of completion:
>
> 1. Whole lines |i_CTRL-X_CTRL-L|
> 2. keywords in the current file |i_CTRL-X_CTRL-N|
> 3. keywords in 'dictionary' |i_CTRL-X_CTRL-K|
> 4. keywords in 'thesaurus', thesaurus-style |i_CTRL-X_CTRL-T|
> 5. keywords in the current and included files |i_CTRL-X_CTRL-I|
> 6. tags |i_CTRL-X_CTRL-]|
> 7. file names |i_CTRL-X_CTRL-F|
> 8. definitions or macros |i_CTRL-X_CTRL-D|
> 9. Vim command-line |i_CTRL-X_CTRL-V|
> 10. User defined completion |i_CTRL-X_CTRL-U|
> 11. omni completion |i_CTRL-X_CTRL-O|
> 12. Spelling suggestions |i_CTRL-X_s|
> 13. keywords in 'complete' |i_CTRL-N|
I've tried some of them (tags seems the most promising), but they
don't work quite as I extpected.
I've programmed a lot in Visual-C++ and when I'm talking about
auto-completion I mean mostly things like the editor supplying a
dropdown list
of the member variables of a structure after you type foo-> for
example, or giving you
the names of the functions visible from the current file and the files
it includes, and the files
they include, etc.
I know how to use ctags to create tags file, and I can use it to parse
the standard headers for python, but even with tags, the auto-
completion I get
is not aware of the scope of variables/namespaces/classes
--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
No comments:
Post a Comment