On 26-Jun-2013 17:38 +0200, Charles Campbell wrote: > Yukihiro Nakadaira wrote: >> On Wed, Jun 26, 2013 at 11:31 PM, Charles Campbell >> <[email protected] <mailto:[email protected]>> wrote: >> >> I tried it again with simple.vimrc: >> >> set nocp >> syn on >> >> >> ":filetype plugin on" is also required to reproduce. >> ftplugin/vim.vim executes ":set iskeyword+=:" >> >> I tried the patch and it seems not fix that strange highlighting. >> > I just did a pull from the Merc repository; the system ftplugin/vim.vim > I got from it does not have set isk+=: in it. Is this your own change? > Anyway, it seems that that's your problem.
The runtime update of Vim 7.3.488 (changeset 2cfb68fa26cd) adds ":" to 'iskeyword'; ostensibly "To make syntax highlighting of 'vimVar's work correctly". Since you, Charles, maintain the Vimscript syntax, I'd thought this actually came from you. (I had earlier complained about the intransparent and infrequent change process of runtime files in Mercurial; this is one instance where it hurts.) I'd like to object against this change, not just because of the current issue, but this also breaks tag jumping, because ctags puts functions without the scope prefix into the tags database. (And this is better, because prefixes are sometimes optional, and <SID> and s: are equivalent.) Therefore, Charles, can't you make "vimVar's work correctly" without adding ":" to 'iskeyword', and send a corresponding patch (for both syntax/vim.vim and ftplugin/vim.vim) to Bram?! That would solve both the broken syntax and the broken tag jumps. -- regards, ingo -- -- 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.
