pansz wrote:
> Ben Fritz 写道:
> > One solution might be to create a custom command that calls cstag, and
> > specifying -complete=tag. Then, in addition to using cscope, generate
> > a tags file. I'm not sure what that would gain, though (probably
> > nothing). I tend to use tags for jumping to definitions, and cscope
> > for most other things.
>
> That should work, the problem is to generate the tags file.
>
> The cscope database takes a long time at the first time, and for any
> future update, it is fast, since it only update those changed.
>
> The ctags does not have such an "update database mode", it generates the
> whole database everytime.
>
Well, maybe this is a good reason to use the custom command method,
then. Generate the tags file once, and use it solely for providing tag
completion in your custom command. Use cscope for navigating the code.
The tags file should contain most of the symbol names even if they're
at outdated positions. When it gets too out-of-sync, you can update
tags again, but it shouldn't need to happen all that often.
Hmm...I think I may try this method, for the reasons here outlined.
Does anyone know if there is a way to specify completion type for
individual arguments? I want a command that takes 2 arguments, the
first being c, d, g, s, etc. and the second having tag completion. I
suppose it wouldn't be the end of the world for both args to have tag
completion but it would not be as nice.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
