It was superseded by g:vue_pre_processors (#133)
I could add a message if g:vue_disable_pre_processors is set, asking
people to update their config to the new variable, but I'd rather not
interrupt people's workflows.
close#131
Setting this option seems to do more harm than good. To avoid confusion, it's better to remove it altogether.
Currently, the recommended approach to use existing plugins for HTML, CSS or JavaScript, is to explicitly configure that plugin to support Vue files.
The change in commit ba9a3dbc4e is
documented in the README, to augment the information regarding
pre-processor languages and g:vue_disable_pre_processors.
* Remove Typescript section. As long as the highlighting "just works", a section in the FAQ shouldn't be needed.
* Fix typo
* Add some more explanation
* Add links to referenced plugins
* removed preprocessing langs from registration
I'm not sure if this will work
* add back support for pre-processors
adds back support for preprocessors, but keeps vim fast when not in use
* completely removed support for preprocessors
testing to see if completely removing preprocessor language registrations will make syntime reports more performant
* added back conditional support
conditional support should work now
* just testing remove all preprocessor support
* I think this will work
* i found the actual bug
some regex statements are being checked several times
* quick fix for now
I only apply a quick fix until I can get to the root of the problem. For this, in order to turn off the preprocessors which seem to bog down vim, just put `let g:avoid_pre_processors = 1` in the .vimrc (or neovim equivalent).
* forgot endif statement
* testing behavior
* removed line to test behavior
* Update readme.md
* Update readme.md
* Update vue.vim
* Update vue.vim
* Update readme.md
