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.
Line under quote is not considered part of quote
See original GitHub issueApologies if this just an issue on my side. But I found that the follow two lines would not be joined into the same quote, when passed to my custom renderer:
> first quote line
second line underneath
I assumed they would both be passed together to the block_quote function.
Issue Analytics
- State:
- Created 3 years ago
- Comments:21 (4 by maintainers)
Top Results From Across the Web
Extended Rules for Using Quotation Marks - Purdue OWL
If the original quote is too long and you feel not all the words are necessary in your own paper, you may omit...
Read more >Ellipsis Use in MLA Style | University of Houston-Victoria
In this case, it's clear that the writer is not quoting the entire speech or even an entire sentence. Importantly, MLA advises writers...
Read more >Quotation Marks and Direct Quotations - University of Sussex
Note first that what is enclosed in quotes must be the exact words of the person being quoted. Anything which is not part...
Read more >Using Ellipses to Omit Words From a Quotation - IUP
Do you have a quotation that is too long and mostly meaningless? You can use an ellipsis to leave out extra or unnecessary...
Read more >MLA Style Guide: 8th Edition: Block Quote
The block format is a freestanding quote that does not include quotation marks. Introduce the block quote with a colon (unless the context...
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 is fixed in v3.
I’m working on a new way to write the parser, which will make it easier to solve problem like this. Pure regex is just very hard to fix this problem.