It's close enough to be readable code, but is not the exact thing. What I meant is that the syntax highlight that I see in vs code is not what gets printed. I am aware of the use of highlight.js and vscode for language detection. Syntax colouring does not require specific pathing. I believe Stack Overflow recently switched to using the same library. VS Code Printing is written so that when VS Code knows what language, I instruct highlight.js to treat the text as a specific language, otherwise I fall back to using highlight.js language detection. One reason I chose it is its extraordinary breadth of support for languages. VS Code Printing uses highlight.js to do syntax colouring.
This still a needed built-in feature from my point of view. This is normal from languages unsupported by the current VsCode instance, but is unintuitive and annoying otherwise. Meaning if I got C/C++ code and want to print it with either VS Printing or PrintCode, both have no clue how to properly highlight the code, without manual input from the user. Using an extension doesn't allow for easy syntax highlighting.
0 kommentar(er)
