I've attempted reaching both the current shell syntax file maintainer as well as the prior one, both at the emails listed in the syntax file itself as well as on their own personal websites. The emails which didn't bounce haven't been answered in several weeks, so I'm posting here per the contributing guidelines.
Here is a commit which aims to fix the issue: https://github.com/binaryphile/vim/commit/47691129d67a31ec8b633b9b78a707b91919aa2c The file is runtime/syntax/sh.vim. The problem: Although the POSIX spec is slightly vague on the point, both bash and dash have behavior which differs from vim's syntax highlighting guidance. I haven't tested against other POSIX shells, nor do I know if earlier versions of bash/dash behaved differently, but current versions do not. The following code is valid bash/dash (two spaces in the terminal " EOS"): read myvar <<' EOS' some string text EOS However, the syntax highlighter fails to recognize the terminal string " EOS". It instead strips the whitespace, which results in the rest of the file being highlighted incorrectly as a string. If you modify the code like so, it tells you that the string is terminated, when in actuality it is not: read myvar <<' EOS' some string text EOS That's it. Ted -- -- 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/d/optout.
