On 11/01/09 15:26, Jonathan Hartley wrote:
> On Jan 11, 6:19 am, Tony Mechelynck wrote:
>> On 11/01/09 01:26, Jonathan Hartley wrote:
>>> On Sat Jan 10 09:38:51 CST 2009, jonathan hartley 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 I'm doing
>>> Note also as an extra clue/red-herring, that there are only two entries
>>> in this dropdown. There were four on the Windows screenshot because it
>>> was failing to filter out directory names. I do not know why directories
>>> are filtered out on Ubuntu but not on Windows, but this may be an
>>> irrelevant distraction.
>>> Will report back if I figure it out.
>> There probably is no "system vimrc" on Windows, but there may be one on
>> Ubuntu, which is sourced even before your own ~/.vimrc. If there is, its
>> location is displayed near the middle of the output of the ":version"
>> commmand.
>>
>
> Thanks for the input Tony, but I'm not sure I follow. If my
> fuzzyfinder config in .vimrc complains that the variables it is
> setting don't exist (presumably because the plugin isn't loaded yet),
> then surely I want to put that config somewhere that gets run *later*
> than my ~/.vimrc, not before? Or have I got the wrong end of the
> stick?
>
> Thanks,
>
> Jonathan
The system vimrc (if any) is read before your own, you cannot change
that. What you can change is that you can override anything you don't
like in it by something in your vimrc.
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.
You can use the ":scriptnames" command at any time to see which scripts
have been sourced in this session of Vim, and in which sequence (if a
single script is sourced more than once in a single session, only the
first time appears in the list).
Best regards,
Tony.
--
You are here:
***
***
*********
*******
*****
***
*
But you're not all there.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
