On Aug 16, 2013 7:02 AM, "Charles E Campbell" <drc...@campbellfamily.biz>
wrote:
>
> ZyX wrote:
>>
>> I see that all g:vimsyn_embed flags say things like “embed … **(but only
if vim supports it)**”. This is ridiculous:
>
> Ah, I disagree -- not ridiculous at all. What's ridiculous is to assume
that one will be writing code for an interpreter embedded in vimscript
without being able to test it. Thus, one needs to have the interpreter
supported for it to make sense. The syntax/vim.vim script is quite long
already; making all interpreters' embedded highlighting work all the time
means everyone would have to put up with additional delays -- and frankly,
I don't think that most folks use all the interpreters. That's not a
problem for those with fast machines; not all have fast machines.
This word should be attached to the inability to force the highlighting.
The case you describe here is targeted with different (computable) defaults
I suggested later in the mail.
>> ou 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.
>
>
> You can look at the embedded code already -- it just won't have the
embedded interpreter's highlighting if your vim won't support it. Sort of a
visual flag that it won't work with your vim.
There are no such flags for all other disableable features except for :syn
cchar (but not :syn conceal and :syn concealends) which is inconsistent.
I should also say that highlighting cchar as an *error* without +conceal is
a bug.
>
>
> --
> --
> 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.
--
--
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.
