Instead of setting it by default, I initially only added this as a tip
to the readme, because it is said to be slower. However, I don't really
notice a performance difference, and when the highlighting isn't working
reliably without it, I think it's better to just include it by default.
With #128, I can imagine some people don't want vim-vue to scan for new
languages on each text change event. So instead of only having an 'auto'
option, users will be able to choose between 'detect_on_enter' and
'detect_on_change'.
When g:vue_pre_processors is set to 'auto', register pre-processors
automatically based on the file's contents, when the file is first
opened.
This works towards #128
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.
* 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
Removes omit_attr argument from s:register_language(), because html,
javascript, and css regions were the only ones that used it, and they
are now handled by syntax/html.vim.
`runtime! syntax/html.vim` also has the advantage that we can hook into
the html syntax, meaning that we can add stuff like highlighting
javascript expressions inside vue directives, and add our own html
attributes.
Also removes the start of line limitation introduced in previous commit
In #46, the question was where to put this option, and why some other
plugins put it in the 'after' directory. Vim-javascript puts it in the
'after' directory because they want to keep the settings in the ftplugin
shipped with Vim, and only add the 'suffixesadd' option. Since Vim
doesn't ship with a Vue plugin, we can safely put this option in ftplugin.
Adriaan Zonnenberg