> On 2009-12-30, Benct Philip Jonsson wrote:
>> Whenever I do a set filetype=mason, or it is done from
>> any file in ~/.vim/ I get an error (translated by me from
>> Swedish, so the actual English wording may be different):
>>
>> "Error detected while processing of Syntax Autocommands
>> E484: can't open file /usr/share/vim/vim71/syntax/mason.vim"
>>
>> /usr/share/vim/vim71/ doesn't exist anymore on my machine,
>> but I don't get the error with other filetypes. The error
>> is not anywhere in ~/.vim/, as far as I can tell.
>>
>> Doing ln -s /usr/share/vim/vim72/ /usr/share/vim/vim71/
>> "fixes" the problem, but I guess there is a proper way,
>> and a real error somewhere with something specifically
>> naming /usr/share/vim/vim71/ when it shouldn't.
>> How can I find out?
>
> I would start with
>
> grep -R vim71 ~/.vimrc ~/.vim
Thanks!
For some reason I forgot to grep for vim71 in ~/.vimrc,
and indeed there was a culprit -- an autocommand which
apparently could be commented out without consequences.
/BP
--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
No comments:
Post a Comment