> You say "decouple" which means "make them less dependent on each other". But > your examples seem to be asking for making various commands more > context-aware, which would probably be *more* coupled to syntax, not less. > Which do you want?
What I mean by this is that there are things like 'iskeyword' and 'isident' and 'define' and 'commentstring', options which are -- or, at least, could be -- relevant to the syntax of the file type, which could be perhaps better and more ubiquitously handled by Vim's syntax functionality rather than a pattern option. It seems to me as though we have a perfectly good hammer for this nail, and we're reaching for the screwdriver. This is what I mean by decoupling syntax features from other features; make syntax-dependent configuration dependent on the syntax functionality, and not on options that are in many cases untouchable on penalty of everything breaking. I'm also calling for additional usage of the syntax functionality to make scripting for file types easier -- for example, it would be useful to have a built-in search function that allows you to specify syntax group matches in addition to pattern matching. I cite again the example of tag jumping -- using more flexible syntax concepts like "identifier" instead of the less code-aware "word" when determining what tag to jump to could be useful. -- -- 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.
