See image (also attached): http://i.imgur.com/wdC6vUK.png
I've reproduced this in OSX and Red Hat, on terminal vim versions 7.2, 7.3,
and 7.4. I don't have access to gVim but I did reproduce this problem on
MacVim, as well as in terminal vim over ssh.
Steps to reproduce:
Configuration doesn't matter, so for example:
$ vim -u NONE
Turn on syntax highlighting and set filetype to vim:
:set ft=vim
:syntax on
In insert mode, type something like:
map ( foobarbaz
Type other syntactically correct vimscript after that and observe the
results. The highlighting should appear wrong until you put in a close
parenthesis somewhere.
It doesn't happen with any other mapping (omap, xmap, vmap, etc.), with
recursive maps (noremap, onoremap, inoremap, etc), or when mapping to any
other character I've tried (even *[* and *{*). The mapping itself works,
despite the incorrect highlighting.
In the source, I think it has to do with line 324 (of the 7.4 source
posted) in runtime/syntax/vim.vim; that line lists all mapping types (and
variants) except `map` itself, which could be the issue. I haven't tested
it, though.
Regards,
Josh
--
--
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
<<attachment: Screen Shot 2014-01-10 at 1.13.04 AM.png>>
