Martin Aeschlimann

Results 69 issues of Martin Aeschlimann

Admittedly a very minor point and I can certainly live without this, but a hex literal, e.g. 0x1.1e7f4707fc4dcp-9 doesn't seem to be handled properly in the syntax highlighting.

_From @nickoz5 on December 20, 2017 6:9_ - VSCode Version: Code 1.19.0 (816be6780ca8bd0ab80314e11478c48c70d09383, 2017-12-14T12:06:43.492Z) - OS Version: Windows_NT x64 10.0.16299 - Extensions: Extension|Author (truncated)|Version ---|---|--- svn-scm|joh|1.4.6 Go|luk|0.6.70 python|ms-|0.9.1 cpptools|ms-|0.14.5 PowerShell|ms-|1.5.1...

_From @dstorey on December 26, 2015 10:43_ Works correctly in the parser for linting and in Intellisense, but isn't syntax highlighted as missing from css.plist ![screen shot 2015-12-26 at 2...

_From @david-russo on October 11, 2016 10:38_ - VSCode Version: 1.6.0 - OS Version: Windows 7 (64-bit) Steps to Reproduce: 1. Open a new file a select the Java language...

_From @dgolub on February 12, 2016 22:22_ When editing Java in Visual Studio Code, import directives are shown with the package names in blue as if they were keywords. They...

_From @Matthijs-Wessels on December 22, 2015 23:24_ The coloring of java enums if off when you add values. The strings in the below example will be colored as if it's...

From https://github.com/microsoft/vscode/issues/160143 ![](https://i.imgur.com/V9QiGQN.png) `

From https://github.com/microsoft/vscode/issues/64067 https://developer.mozilla.org/en-US/docs/Web/SVG/Element/svg tag in element is marked as invalid / red tag name, but the following is perfectly valid svg: Though the inner gets marked red. ![image](https://user-images.githubusercontent.com/3669616/49327947-6d107880-f568-11e8-95d3-5eff6300b1c1.png)

From https://github.com/microsoft/vscode/issues/77889 **VSCode Screenshot ** **Steps to Reproduce:** 1. Use attributes with and without upper casing onClick, onclick, etc. ``` ``` 2. Colors are different. onClick is an 'unknown' attribute

The following code doesn't highlight correctly in VSCode after ` //`. The problem is that the embedded JavaScript grammar consumes the full `//` and the sourrounding html rule doesn't end....