On Thu, Jul 17, 2008 at 14:27, Nikolai Weibull <[EMAIL PROTECTED]> wrote:
> Posting sooner rather than later is always better. That almost rhymes. True. I simply always forgot by the time I was finished fiddling with my scripts. > However, why would you name a variable do? I wouldn't. I named one variable test, but do was shorter to write in my email :) > Also, why are you putting semicolons after do? I am using shortloops 99% of the time and thus always forget where to put the semi-colons. Slobbering the thing with them works, so I adapted that 'style'. > This particular case can be solved by matching paths, but how about > arguments to commands in general, for example: Indeed. That is (almost) the only situations I saw the issue rear its head, too. In that case it was ~/.zsh/functions, but again, 'do' is faster to read & write. The other situation woud be echo yes I do > 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. I know that this is not feasible or at least not worthwhile in terms of work and gain. I only mailed the list because I knew they would be easy to fix. > 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. Agreed :) Thanks for your work, Richard --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
