2008/10/22 Tony Mechelynck <[EMAIL PROTECTED]>:
> Matchit is not "breaking" anything, it "improves" % matching; however,
> to do that, it relies on a buffer-local variable b:match_words telling
> it what to match: just look up what that variable is set to in:
> - a Vim script,
> - an HTML file,
> - an XML file
> - a bash script
> - etc.
>
> The above autocommand "restores" matching of round, square and curly
> brackets for these 4 filetypes which don't set the matchit setting in
> their filetype-plugins. However even here there is a plus: with the
> above, and matchit loaded at startup, you won't anymore pair a bracket
> within a comment with its opposite outside a comment.
>

if has('autocmd')
       augroup vimrclocal
       " match (:),[:],{:} in matchit for C, C++, CSS and javascript
               au FileType c,cpp,css,javascript,php
                       \ let b:match_words = &matchpairs
       " you may have other autocommands, unrelated to the above.
       " Place them here.
       augroup END
endif

I mainly edit .html and .php files so I added php to the FileType list
when adding this to my .vimrc. After this normal bracket matching
works for .php files  but I lose the html matching, html matching
works fine on .html files but no bracket matching.

How do I view the buffer? I'll send in the entries from the different
file types.

Re upgrading, it is a managed server and they will upgrade if I ask
for it but as it then becomes a non-standard setup and is no longer
supported. The version of vim is the least of my problems on that box!

Robin

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to