> 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.

I second the request and can add another reasons:

- It breaks python << EOF highlighting: `try:`/`else:` and so on is too common 
in python code.
- It breaks using `*` for searching for function argument (in function 
definition there are no `a:`).
- It breaks completion for functions with unique argument names (for the same 
reason) and completion for standard names (e.g. with consistent coding style 
there may be `l:repository` (`repository`) and `a:repository` at the same time).
- It breaks expectations of how searching works: if I want to find some word in 
comment using `\<works\>` I definitely not expect that `works:` in this 
sentence is not matched. I also would not expect searching for `\<works:\>` if 
I press `*` on `works:` in this sentence. It is hard to keep different habits 
for different filetypes. `-` in `isk` in zsh files is already too bad, do not 
make it worse by adding third filetype to a list.

-- 
-- 
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.


Raspunde prin e-mail lui