Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Invalid syntax coloring when using : in a multiline value in a yaml file
See original GitHub issueusingmultiline: |
should be green
should also be: green
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
How do I break a string in YAML over multiple lines?
Your solution refers to a different problem: in your case you want linebreaks to appear in rendered HTML as result of processing YAML....
Read more >Incorrect highlight color of yaml multi-line text values
Incorrect highlight color of yaml multi-line text values ... In YAML, one can use > and | for multiline text values. Such values...
Read more >Sub-syntax for string literals - Pitches - Swift Forums
The idea is a new feature for multi-line string literals that allows the user to specify what format the nested content should conform...
Read more >YAML: The Missing Battery in Python
Note: The YAML specification forbids using tabs for indentation and considers their use a syntax error. This coincides with Python's PEP 8 ...
Read more >Syntax - Neovim docs
Syntax highlighting enables Vim to show parts of the text in another font or color. ... This means you should use the right...
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 Free
Top 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
@apupier this should be fixed with the latest tm4e release.
I also tried putting the current grammar from Wild Web Developer into VSCode locally to see how it likes it or not, and while I could see some other changes I did to verify the grammar was correctly used by VSCode, the current grammar form Wild Web Developer should multi-line properly in VSCode without modification. So it’s definitely an issue in TM4E more than in the grammar. I’ve opened https://github.com/eclipse/tm4e/issues/266