>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.

I hope that the original author doesn't mind me posting this kludge.
I've talked with the author, and he's really nice.

In ~/.vim/plugin/fuzzyfinder.vim, make the s:FormatCompletionItem
look like the function defined here:

http://notesmine.com/fuzzy_finder_kludge

Then, in your .vimrc, put this line:

let g:fuzzy_root=getcwd()

Now, let's say you have a project in projectA directory:

/my/really/deep/directory/of/projects/projectA/myfile.txt
/my/really/deep/directory/of/projects/projectA/src/foo.c

If you CD to /my/really/deep/directory/of/projects/projectA, then
open Vim using the commandline,

You should only see files like:

myfile.txt
src/foo.c

Instead of the files with /my/really/deep/directory/of/projects/
projectA appended to them.

Here's my screenshot:

http://notesmine.com/fuzzy_finder_kludge

--Nate

On Jan 11, 1:19 pm, Jonathan Hartley <[email protected]> wrote:
> On Jan 11, 2:52 pm, Tony Mechelynck wrote:
>
> > Then, global plugins are read after your vimrc. Yet you can override
> > them too: either (if you have only a few changes) by autocommands
> > defined in your vimrc for the VimEnter event (which is triggered at the
> > very end of startup), or if your changes are more extensive, by one or
> > more user scripts at ~/.vim/after/plugin/*.vim (that's on Unix: on
> > Windows, replace /.vim/ by /vimfiles/). These "after" plugins are all
> > sourced just after the plugins in $VIMRUNTIME/plugin.
>
> Understood, many thanks! I'll check out the VimEnter event mechanism
> for now.
>
> My original problem still stands. I'm tinkering with it every couple
> of hours, inbetween getting real work done.
>
> Best,
>    Jonathan
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to