newlisp.vim 1.35
Posted: Fri Apr 15, 2011 7:11 am
I've just realized that I haven't visited this forum for a half-year now. I am still using newLISP, just feeling less social about it. ;-) And now is the time for a new version of the syntax highlighter for the Vim text editor. This version is highly experimental, testing and feedback is highly appreciated. User-visible changes:
* String delimiters ("quotes", {braces}, and [text]tokens[/text]) are highlighted in different color than the string content.
* Bracketed symbols [like this] are highlighted in boldface; no other symbols are highlighted in boldface anymore (the newlispSymbolSpecial group is gone).
* Errors highlighting is drastically changed. The newLISP itself allows tokens to touch without a separator, this leads to very strange code in some cases. For example, 019 is two tokens, not one (digit nine may not occur in octal literal, so it starts a fresh new number). Similarly, one[two] is one single token, but [one]two are two (check this with your newLISP interpreter!). I believe that using this feature in the real code leads to confusion, therefore the adjacent tokens are marked as errors (to be precise, the second of two adjacent tokens is marked as error, this should give you a clue why there are two and not one!). You can see some corner case examples here.
Downloadable from the usual locations (one, two). And again, this is an experimental version, please test it before using in production!
* String delimiters ("quotes", {braces}, and [text]tokens[/text]) are highlighted in different color than the string content.
* Bracketed symbols [like this] are highlighted in boldface; no other symbols are highlighted in boldface anymore (the newlispSymbolSpecial group is gone).
* Errors highlighting is drastically changed. The newLISP itself allows tokens to touch without a separator, this leads to very strange code in some cases. For example, 019 is two tokens, not one (digit nine may not occur in octal literal, so it starts a fresh new number). Similarly, one[two] is one single token, but [one]two are two (check this with your newLISP interpreter!). I believe that using this feature in the real code leads to confusion, therefore the adjacent tokens are marked as errors (to be precise, the second of two adjacent tokens is marked as error, this should give you a clue why there are two and not one!). You can see some corner case examples here.
Downloadable from the usual locations (one, two). And again, this is an experimental version, please test it before using in production!