Hello Bram, hello Charles, dear Readers, for some time now i tried to tackle a bug in highlighting of vim files. Namely the highlighting of 'vimVar's with and without scope prefixed. Look at the attached sample.vim with default highlighting for vim files to see what i mean. I tried to find a solution for this without breaking too much other stuff and so far the solution seems to be to add 'isk+=:' for vim files. Therefor i propose this change in 'runtime/ftplugin/vim.vim' patch attached and at the same time ask everyone to test this if it breaks anywhere for you.
Thanks. -- Regards, Thilo 4096R/0xC70B1A8F 721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F -- 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
sample.vim
Description: application/wine-extension-vim
--- vim.vim.orig 2012-03-18 12:26:05.000000000 +0000 +++ vim.vim 2012-03-20 19:34:00.000000000 +0000 @@ -21,6 +21,10 @@ " and insert the comment leader when hitting <CR> or using "o". setlocal fo-=t fo+=croql +" to make syntax highlighting of 'vimVar's work correctly we need the colon to be +" part of keywords. This needs to be done prior to the 'isk+=#' below. +setlocal isk+=: + " To allow tag lookup via CTRL-] for autoload functions, '#' must be a " keyword character. E.g., for netrw#Nread(). setlocal isk+=#
vim.vim
Description: application/wine-extension-vim
