Re: Strange highlighting

Phil Dobbin wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 25/01/2012 21:41, Charles Campbell wrote:
>
>> Phil Dobbin wrote:
>>
> [...]
>
>
>>> As a follow up to this I've discovered the odd highlighting only
>>> occurs when passing an argument to Vim i.e `vim .bashrc`
>>>
>>> If I start Vim& then edit the same file all is OK.
>>>
>>>
>
>
>> Well, I was thinking that perhaps your termtype database was incorrect,
>> but that should affect :e .bashrc, too.
>>
>> So, what's the filetype?
>>
>> vim .bashrc
>> :echo&ft
>>
>> Do files other than shell script files appear odd?
>>
>> Does
>>
>> vim -u NONE .bashrc
>> :set nocp
>> :syn on
>>
>> have odd highlighting?
>>
>
>
>
> Running the first instance the filetype returns `sh`.
>
> In the second there's no odd highlighting when the commands are run.
>
I'm afraid that I'm not certain what you're saying here -- does the
third question, with "vim -u NONE .bashrc", have no odd highlighting?
In that case, it seems likely that you've got a plugin problem or
something odd with your .vimrc. Would you care to post your .vimrc?
If its a plugin problem, may I suggest that you

cd .vim
mv plugin PLUGIN
mv ftplugin FTPLUGIN
and then move files, one at a time, from PLUGIN (or FTPLUGIN) to their
corresponding lowercase directory and try "vim .bashrc", looking for
odd highlighting. When it occurs, you'll at least know which
plugin/ftplugin is involved.
> The odd highlighting also occurs in text files, python& perl scripts.
> It doesn't happen in helpfiles but I guess that's because Vim's already
> running.
>

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php