zhangyuting / vim

Automatically exported from code.google.com/p/vim
0 stars 0 forks source link

load html.vim error #163

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. vim *.html
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
vim 7.4 on ubuntu12.04

Please provide any additional information below.
I compile vim7.4 in this way:
./configure --enable-pythoninterp=yes --enable-xim --enable-multibyte 
--enable-cscope --enable-largefile --disable-gui --with-x --with-features=huge 
--enable-fontset

the "css.*Attr" cannot be recognized.

Original issue reported on code.google.com by kos19...@gmail.com on 23 Aug 2013 at 2:46

Attachments:

GoogleCodeExporter commented 9 years ago
I believe this is fixed with the latest runtime files. If not, please report 
the problem to the maintainer of the file. He will then send updates to Bram 
for inclusion.

Original comment by chrisbr...@googlemail.com on 30 Sep 2014 at 8:56

GoogleCodeExporter commented 9 years ago
I don't think this is fixed, according to my test, this bug is still alive.

I don't think this is a bug caused by runtime file. This might be caused by 
"syn include". If i remove css.*Attr, html.vim can be parsed correctly, then 
remove css.vim, the css.*Prop cannot be parsed correctly. This means only 
css.*Attr are lost after "syn include".

Original comment by kos19...@gmail.com on 11 Oct 2014 at 2:27

GoogleCodeExporter commented 9 years ago
Okay, then how do you reproduce the problem? Start with vim -u NONE -N -c 
'command1|command2' *.html

Original comment by chrisbr...@googlemail.com on 11 Oct 2014 at 7:50

GoogleCodeExporter commented 9 years ago
Sorry to waste your time, it's my fault, I forgot the plugins. This problem is 
caused by a css3 syntax plugin.

Original comment by kos19...@gmail.com on 12 Oct 2014 at 3:16

GoogleCodeExporter commented 9 years ago
Okay, closing as inalid. You should take that problem to the plugins maintainer.

Original comment by chrisbr...@googlemail.com on 12 Oct 2014 at 7:13