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 am not completely clear on your question. You can always generate a single tag file which includes all the directories that you would visit. Normally, for development branches, this is easy as you can generate the tag file right at the root of the branch, including everything under it. If your usage scenario is such that the directories that you visit are scattered all over the filesystem, then you should still be able to create a command that will build a central tag file for all these directories. The sample find command given can be extended for this case, as the find manual suggests that you can have multiple "paths". Create a script and have it run on demand or through a scheduler. You can of course generate a single tag file for your entire filesystem, but you will have to consider performance issues, both in building the file and using it with the plugin. > > - It seems that I can't locate file named "aaabbb" thru directly typing > "bbb", do I always have to locate file begin with the first letter of > the filename? This is strange. The pattern is not achored to the start, so this shouldn't have happened. What I am guessing is that the lookup didn't actually trigger because you only typed 3 characters. If you read the help section on |lookupfile-settings|, you would find information on a setting called g:LookupFile_MinPatLength that explains what it is and why it is set to a value of 4 by default. The brief answer is that by default you have to type at least 4 characters before the lookup gets triggered. Since it is a Vim regex, you can easily fool it by type ".*.*" to match all, or in this specific case "bbb.". > > Thanks > Eddy Let me know if this answered your question and solved your problems. If you need any other specific features to meet the ido.el, let me know and I will try to help (as long as they are reasonable enough to implement). -- HTH, Hari > > 2006/8/8, Yakov Lerner <[EMAIL PROTECTED]>: > > On 8/8/06, Eddy Zhao <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > Does anyone ever used ido.el in emacs? (www.cua.dk/ido.el) > > > The plugin could considerably speedup file accessing performance, > > > especially when I'm maintaining a large wiki docbase. So I really > > > want to know > > > - if vim have equivalent plugin like ido.el > > > > This question was raised on the list ~1/2 years ago, and Hari > > created the file-selection plugin in response: > > http://www.vim.org/scripts/script.php?script_id=1581 > > "lookupfile : Lookup files using filename completion" > > > > There are several plugins dealing with recently-used files, on > > vim.org. > > > > Vim mappings and functions can be used to open often-used files > > quickly. gf command is helpful, too. NB that vim has built-in > > recursive filename completion (**/xyz<tab>) as well as simple filename > > completion (<tab>). > > > > Yakov > > > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
