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.
Single line comment error
See original GitHub issue\[ x = 1 % comment \] results in an error. The error goes away if a linefeed is placed after the comment.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Single line comment continuation - c++ - Stack Overflow
These comments do not nest. The characters // start a comment, which terminates with the next new-line character.
Read more >How does Single-line comment feature work and can it be ...
Single-line comments are preceded by // and end at a newline character, carriage return, or end of file. To be properly interpreted as...
Read more >Single-line comment or end-of-line expected - MSDN - Microsoft
I add the line at the first lin of cs file. But is appears the error message as below: Single-line comment or end-of-line...
Read more >Single line comments throw error · Issue #74 - GitHub
// single line comments inside a style block will produce an error. I frequently use these to quickly test something and then possibly...
Read more >Why doesn't CSS allow single-line comments? [closed]
CSS is defined with very precise "error-tolerant" parsing rules which means even if you write something syntactically illegal there are precise ...
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
This has turned up a bug in
\href:\href{x%y}{hi}works fine if it’s a single line, but a multiline input likecauses the comment behavior to trigger, resulting in an unclosed
{. LaTeX doesn’t work this way (despite the syntax highlighting above), because\hrefredefines how%works. I think we’ll need to fix this in the same way that\verbworks.Yeah, this should be a strict mode only behaviour.