On Thu, Jul 17, 2008 at 12:30, Richard Hartmann <[EMAIL PROTECTED]> wrote:
> Syntax elements are detected & highlighted in the wrong places. > Two examples I have known for some time but never got around to > do much about them are: Posting sooner rather than later is always better. That almost rhymes. > for do (foo bar); do; echo $do; done > foreach do (foo bar); do; echo $do; done Fixed. for and foreach now have a nextgroup=zshVariable that takes care of this. However, why would you name a variable do? Also, why are you putting semicolons after do? > /do/not/highlight This particular case can be solved by matching paths, but how about arguments to commands in general, for example: grep do *.zsh? To not highlight keywords in this situation would require us (and by that I mean me) to implement the whole Zsh grammar. Please take a look at Src/parse.c before asking me to do that. Overall I think that syntax/zsh.vim does a very good job of highlighting Zsh source files. I can live with a few blemishes if they require substantial complexity to fix. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
