I see that all g:vimsyn_embed flags say things like “embed … **(but only if vim
supports it)**”. This is ridiculous: you don’t have to have vim lua support to
code in lua and have syntax highlighting; you specifically don’t have to have
vim lua support to write or watch lua<<EOF sections; and it is completely
possible for oneself to want to review {interp}<<EOF sections in foreign
plugins before deciding whether he needs to obtain Vim with {interp} support or
(my case) to watch correct highlighting of his own vimrc on machine without
specific interpreter support.
I thus see no reason for using `(g:vimsyn_embed =~ 'p' && has("perl"))` checks
without any option to always highlight embedded perl code. If the intention is
to indicate that interpreter is not supported then the only place where
`has("perl")` should be present is the section where `g:vimsyn_embed` default
value is computed: those (almost every vim user) who do not set
`g:vimsyn_embed` will not notice any change in behavior, those who care will
always receive correct highlighting.
--
--
You received this message from the "vim_dev" 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
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
