Code Syntax Highlighting not Working
See original GitHub issueHello, great plugin,
After following the Syntax highlight
section of the README the code, as in your examples, is not highlighting:
Inline `code` has `back-ticks around` it.
> ```javascript
> var soop = "JavaScript syntax highlighting";
> alert(s);
> ```
>
> ```python
> s = "Python syntax highlighting"
> print s
> ```
Any ideas what could be wrong? Thanks
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
Visual Studio Code syntax highlighting not working
I am using Visual Studio Code (VSC) as my IDE. My computer just updated to Catalina 10.15. 2 (19C57) and since the update,...
Read more >Syntax highlighting not working : r/vscode - Reddit
I've tried to reinstall vscode, completely whipping existing settings, but nothing works. Any help would be appreciated!
Read more >Syntax highlighting not working for Python in VS Code with ...
Uninstalling the Python for VSCode extension fixed the issue. All reactions.
Read more >Setting up code syntax highlighting using the Visual Studio ...
The syntax highlighting was the first Language Server Protocol feature in 4D v19 R6. Let's see how to customize your source code rendering....
Read more >How to enable semantic highlighting in VS Code - Stefan Judis
Semantic syntax highlighting makes sure your source code is not only beautifully colored, but that used the colors are logical, too. After ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@ghiscoding this is due to the fact that leading/trailing whitespaces are meaningful in markdown because they serve a purpose.
For this reason, when you are doing the following … it means you want white spaces in front of lines 4 and up:
By doing the following … you are removing leading spaces in front of lines 4 and up:
Honestly I always found it easier to use
src
input property to fetch remote files as it has the following advantages:@jfcere Thanks for the explanation, I guess that is why you added this new
ngPreserveWhitespaces
and delete the white spaces by default in the newer version. I guess what I could do on my side to quick fix this is to simply remove all white spaces myself from the variables. that should work too. I understand now thanks.