On 19/06/09 19:39, Gary Johnson wrote:
>
> On 2009-06-19, Tony Mechelynck wrote:
>> On 19/06/09 09:07, pansz wrote:
>>>
>>> Tony Mechelynck ??????:
>>>> And if you're on Windows, replace $HOME/.vim by $HOME/vimfiles
>>>> everywhere above. (Vim can use forward slashes as path separators, even
>>>> on Windows.)
>>>>
>>>> Best regards,
>>>> Tony.
>>>
>>> This is known to cause inconveniences, I hope some future versions of
>>> vim will use the same directory.
>>>
>>> There are some work-around, such as ln -s vimfiles .vim. But I don't
>>> think it is elegant enough, vim is a cross-platform editor and should
>>> keep the same behavior on different platform as possible.
>>>
>>> i.e. in Windows vim could search for $HOME/.vim before $HOME/vimfiles,
>>> this remains compatibility with most non-windows versions and compatible
>>> with users who expect the $HOME/vimfiles directory.
>>
>> There are reasons for these differences:
>> - On Unix, but not on Windows, file and directory names starting in a
>> dot are "invisible". Most configuration files (under $HOME) are of this
>> kind. If you want to make something hidden under Windows, use e.g.
>>
>> attrib +H .\vimfiles
>>
>> - On MS-DOS, names should not begin with a dot. I'm not sure they're
>> acceptable on 8.3 systems even if the part after the dot consists only
>> of 3 letters.
>
> Yes, but, ":help .vimrc" says,
>
> Note: For Unix, OS/2 and Amiga, when ".vimrc" does not exist,
> "_vimrc" is also tried, in case an MS-DOS compatible file
> system is used. For MS-DOS and Win32 ".vimrc" is checked
> after "_vimrc", in case long file names are used.
>
> So, if Vim is flexible enough to check both $HOME/.vimrc and
> $HOME/_vimrc on both DOS and Unix, then it could be made flexible
> enough to check both $HOME/.vim and $HOME/vimfiles in the same
> manner.
>
> Regards,
> Gary
I believe the difference is that the vimrc and gvimrc are sourced only
once at startup (hence, only a small overall performance throwback for
checking both names), while the 'runtimepath' directories are walked
through at practically every autocommand event, and also for ":runtime"
and ":doau" commands. I believe that adding two items in 'runtimepath',
though it would work, might reduce performance somewhat.
I'm not Bram, however; maybe he has something to say on the subject.
Best regards,
Tony.
--
"Beware of the man who works hard to learn something, learns it, and
finds himself no wiser than before," Bokonon tells us. "He is full of
murderous resentment of people who are ignorant without having come by
their ignorance the hard way."
-- Kurt Vonnegut, "Cat's Cradle"
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
