CriticMark issue
// Please enter a detailed description of the issue // Description of the issue: Trying to put a CriticMark comment example into a readme renders correctly via multimarkdown to html but shows spans in marked 2
// Please enter a list of steps required to reproduce the issue // Steps to reproduce:
- create file with the following text
To add comments, you use the markup{>> Comment goes here <<} - display in marked
- you will see
Comment goes here
// If applicable please attach a sample document that causes the issue for you.
// Configuration (do not edit) Marked 2 958 (Direct)
macOS Version: 10.13.6
additionalMathJaxConfig:
allowPageBreakInCode: TRUE
bookTxtIsLeanpub: TRUE
summaryMdIsGitBook: TRUE
codeIsPoetry: TRUE
codeCanWrap: TRUE
collapsibleHeadlines: TRUE
convertGithubCheckboxes: TRUE
convertYAMLToMMD: TRUE
defaultMathJaxConfig: TeX-AMS-MML_HTMLorMML
defaultPreviewStyle: swiss
defaultProcessor: MultiMarkdown
enableMiniMap: TRUE
excludeBlockQuotesFromCounts: TRUE
excludeFootnotesFromCounts: TRUE
excludeVerbatimFromCounts: TRUE
excludeCaptionsFromCounts: TRUE
folderPreviewExtensionsArray: md, markdown, txt, mdown, html, opml
githubNewlines: TRUE
h1IsPageBreak: TRUE
h2IsPageBreak: TRUE
hrIsPageBreak: TRUE
includeMathJax: TRUE
limitTextWidth: TRUE
minimalJavaScript: TRUE
outlineModeExtensions:
permissionGranted: TRUE
printHeaderBottomLeft:
printHeaderBottomRight:
printHeaderFirstPage: TRUE
printFooterFirstPage: TRUE
printHeaderTopLeft:
printHeaderTopRight:
processHTMLFiles: TRUE
removeMetadataForPreview: TRUE
removeYAMLHeaders: TRUE
scrollToEdit: TRUE
shouldDetectCritic: TRUE
shouldHighlightMarkupErrors: TRUE
shouldLoadCritic: TRUE
syntaxHighlight: TRUE
syntaxHighlightOnlyLang: NO
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Brett on 14 Sep, 2018 05:18 PM
This is definitely a Marked issue, but not one I'm going to be able to
get into the bugfix queue immediately. You can work around the issue by
manually adding the code tags and escaping one of the angle brackets:
<code>{\>>Comment<<}</code>
If it's in its own code block, as opposed to inline, you'd want to add
both pre and code tags and not fence or indent the block:
<pre><code>
code example
{\>>Comment example<<}
</code></pre>
Sorry for the inconvenience.
-Brett