On Wed, 9 Aug 2006 at 5:12pm, Charles E Campbell Jr wrote:

> Hari Krishna Dara wrote:
>
> >On Wed, 9 Aug 2006 at 1:02am, Eddy Zhao wrote:
> >
> >
> >
> >>Hi Yakov,
> >>
> >>  Thanks for the prompt help. I tried the lookupfile plugin,
> >>looks great at first glance, can you throw light on the below
> >>problems I encountered
> >>
> >>  - do I always have to generate tagfile for every directory i visited?
> >>    if so, I feel its a big burden that prevent me using the plugin
> >>    frequently and globally. is there any way to eliminate this burden?
> >>
> >>
> I'm sure there is; every time a failure to find a match would require
> Hari's plugin to run ctags over
> all directories you've visited (I'm not sure how he'd get that
> particular list, though).  Of course,
> that means a significant delay every time you try to complete on a
> string that doesn't have a match.
> I'd think that'd be annoying.  OTOH, if you want a map that would
> rebuild the ctags database, that
> should be straightforward.  Again, the kicker is how to know what
> directories you've visited.
> Oh, about the map:  check on help for :map and system().
>
> Regards,
> Chip Campbell

I think OP and Yakov were taking about building the list when there is
none in the current directory, not when the match itself fails. However,
as I said in my previous email that I just sent, there is no standard
tool for building this list. I gave examples of how to use the GNU find
command to do this, but if you don't have it or if your needs are more
complex, you can use other tools or a script to do it. But running the
external command on-demand to build or refresh tags database (which is
used as the file index) using a map as you suggested, or using a
scheduler (to keep it up to date periodically) is all that is required.
I am trying to understand what is the big limitation in this approach.

-- 
Thanks,
Hari

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Reply via email to