Your message dated Fri, 4 Apr 2008 02:14:53 -0400 with message-id <[EMAIL PROTECTED]> has caused the report #473736, regarding vim-runtime: sh syntax problems with comments after `set', keywords, bash's `$""', nested cmd subst to be marked as having been forwarded to the upstream software author(s) Charles E Campbell Jr <[EMAIL PROTECTED]>
(NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 473736: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473736 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems
--- Begin Message ---Charles, The following problems were reported to Debian about the sh syntax highlighting. - Comments after a 'set' command are only highlighted as such if there's a semi-colon to indicate the end of the 'set' command. set -x # highlighted as normal text set -x; # highlighted as a comment - Syntax highlighting for the 'for' and 'if' keywords are a bit lax. This part is two-fold. The first occurs when you have a top-level command with a string that starts with "-for". command -for-foo In this case, "-for" is highlighted as 'shOption'. The other case occurs when for/if/while/case is not the first word on the line -- they are highlighted as if starting a loop/conditional/block. blah () { blah () { command if-foo command for-foo } } It's more obvious inside a block like a function or if/while/for since the closing }/fi/done are highlighted as errors. - Bash's $"" string syntax isn't highlighted, although its $'' is. Thanks for taking a look at these. -- James GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]>
--- End Message ---
