> Update -- Running the new fuzzyfinder.vim (2.19) on Arch Linux doesn't give me > the same hits that I get on OSX.
Another update, the 2.19 version of fuzzyfinder.vim also gives me unexpected results when searching. The new fuzzy finder's algorithm isn't as good with respect to capitalized letters and word boundaries, in my opinion. This is probably not the best place for discussing the fuzzy algorithm, but I'm just thinking out loud :-) For example, if I have two files: EasyGrep nategrep And I type "EG", it should select EasyGrep first, even though in "nategrep" the letters are closer to each other. To me, this is "correct", because I know I'm searching for (E)asy(G)rep, and type in the two most significant letters. If I were searching for "nategrep", I would type in "ng". I think that letters that are on word boundaries, or letters that are capitalized should be weighted higher. Another example is: some_file.txt some_file.rb sinful.txt If I type "sft" I would expect "some_file.txt" to be a first hit. If I were looking for "sinful.txt", I would type "sit" or something like that. The fuzzy finder from Jan. 11th (2.17) works the way I like it. The one from Jan. 14th (2.19) doesn't. So, the new way of searching might be by design, which would be disappointing for me, because I think that Textmate has it right. Or, it could be a bug. Either way, I'll find some time next week to submit this issue to the author. I'd be interested in opinions from anyone who uses the fuzzyfinder.vim plugin. Thanks, --Nate > > I'm running Vim 7.2, patches 1-65 on Arch, and MacVim version ??? on > OSX. > > Oh well, I'll just keep the old fuzzy finder on my Arch box. > > --Nate > > On Jan 15, 2:11 pm, Nate <[email protected]> wrote: > > > >notice while I'm at it that the latest version of fuzzyfind has a comment > > >to > > >the effect that it introduced *exactly* this feature. > > > Ding! Ding! I wanted to make sure that you'd seen the update. > > This is sort of the "Murphy's Law", where if you fix something, then > > the original author will fix it much better than you a week after you > > fix it. :-) > > > It works **awesome** for me in the latest version. I'm on Mac OSX, > > so I don't know about how to fix the problem on Windows. :-(. > > > I would recommend that you e-mail the author and ask. He's very nice > > and responds > > to questions and suggestions. > > > --Nate > > > On Jan 14, 1:22 pm, Jonathan Hartley <[email protected]> wrote: > > > > Hi, > > > > Nate wrote: > > > >> I really like the fuzzyfinder plugin, but when my project is located > > > >> within a mediumly deep directory structure, the matched pathnames that > > > >> it displays in its dropdown are absolute, and hence too long to see > > > >> what > > > > > Johnathan, > > > > > I added a kludge to fix this exact problem. > > > > Many, many thanks for your info Nate! > > > > I'm pouring over all the information very deeply. As I'm sure you > > > realise, the > > > version of fuzzyfinder which you patched is no longer the latest, so I'm > > > trying > > > to squint at the latest version and apply a similar patch. No luck thus > > > far > > > (It's quite different) > > > > I notice while I'm at it that the latest version of fuzzyfind has a > > > comment to > > > the effect that it introduced *exactly* this feature. Perhaps this is why > > > I see > > > it working on Ubuntu out of the box. I am not yet sure why it doesn't > > > work for > > > me on Windows. > > > > If I figure it out, I'll post the results here and mail them to > > > fuzzyfinder > > > author, just in they find it useful. Otherwise I'll revert to an older > > > version > > > of fuzzyfind and use your patch. > > > > Many thanks, > > > > Jonathan > > > > -- > > > Jonathan Hartley [email protected] > > > +44 7737 062 225 http://tartley.com > > > twitter: tartley bio: Made of Meat. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
