I want to suggest some changes to the VIM syntax file. Let me try to summarize everything that's changed:
Keywords: many keywords were missing and I added a lot of them. There are new options to enable color related keywords and three-module related ones.
String constants: previously, only double quoted strings were highlighted and escaped characters were wrong. Now both single and double quoted strings are properly highlighted and special characters for each also work.
Number constants: fixed some errors such as: only lowercase e is recognized now (1.0e10), dangerous implicit scaling such as (0.1.1 = 0.1 * .1) are highlighted as errors.
Comment strings: also allows for both flavors of strings (single and double quoted)
Delimiter matching: unmatched delimiter highlighting has been reviewed, unmatched parenthesis and square brackets causes the next semicolon to be highlighted, which is closer to the source of the problem.
Removed feature: doesn't highlight trailing white spaces as this can be achieved by other plugins.
Potentially controversial change: the last commit limits the column width of the source file, which I don't think it's widely adopted for VimL sources.
The keywords might be worth discussing further, even though I added a lot of them, there are still much more such as all the ones listed in asy-keywords.el. Maybe we could categorize them and add all of them in the syntax file? Or maybe that would be overkill? Many keywords are both functions and variables for instance and without LSP, just populating a syntax file might just lead to some oddities.
I want to suggest some changes to the VIM syntax file. Let me try to summarize everything that's changed:
three-module related ones.eis recognized now (1.0e10), dangerous implicit scaling such as (0.1.1=0.1 * .1) are highlighted as errors.The keywords might be worth discussing further, even though I added a lot of them, there are still much more such as all the ones listed in
asy-keywords.el. Maybe we could categorize them and add all of them in the syntax file? Or maybe that would be overkill? Many keywords are both functions and variables for instance and without LSP, just populating a syntax file might just lead to some oddities.