Misinterpretation of Bear's markdown
// Please enter a detailed description of the issue // Description of the issue:
When using Marked2 to do a live preview of a Bear note, sometimes the parsing/interpretation goes wrong, which can be solved by adding an extra newline after the paragraph or line before the point where things go wrong.
// Please enter a list of steps required to reproduce the issue // Steps to reproduce:
- Type a piece of text with at least two headings in it (heading, text, heading, text)
- Make sure there are NO additional newlines after the heading and the body parts.
- In markdown:
# heading body text….
# next heading body text. - The second heading shows up exactly as typed (hash space heading text) instead of an actual heading.
- Insert an additional newline after each body text part and the problem goes away.
// If applicable please attach a sample document that causes the issue for you.
// Configuration (do not edit) Marked 2 1027 (Mac App Store)
macOS Version: 12.2.1
additionalMathJaxConfig:
allowPageBreakInCode: YES
bookTxtIsLeanpub: NO
summaryMdIsGitBook: NO
codeIsPoetry: NO
codeCanWrap: YES
collapsibleHeadlines: YES
convertGithubCheckboxes: YES
convertGithubEmoji: YES
convertYAMLToMMD: NO
defaultMathJaxConfig: TeX-AMS-MML_HTMLorMML
defaultPreviewStyle: 100
defaultProcessor: MultiMarkdown
enableMiniMap: YES
excludeBlockQuotesFromCounts: NO
excludeFootnotesFromCounts: NO
excludeVerbatimFromCounts: NO
excludeCaptionsFromCounts: NO
folderPreviewExtensionsArray: md, markdown, txt, mdown, html, opml
githubNewlines: YES
h1IsPageBreak: NO
h2IsPageBreak: NO
hrIsPageBreak: NO
includeMathJax: YES
includeKatex: NO
limitTextWidth: NO
mathNumberEquations: NO
mathNumberEquationsSide: 0
mathNumberEquationsAMSOnly: NO
minimalJavaScript: NO
outlineModeExtensions:
permissionGranted: NO
printHeaderBottomLeft:
printHeaderBottomRight:
printHeaderFirstPage: NO
printFooterFirstPage: NO
printHeaderTopLeft:
printHeaderTopRight:
processHTMLFiles: YES
removeMetadataForPreview: NO
removeYAMLHeaders: NO
scrollToEdit: YES
shouldDetectCritic: YES
shouldHighlightMarkupErrors: YES
shouldLoadCritic: NO
syntaxHighlight: NO
syntaxHighlightOnlyLang: NO
useCustomMarkdownProcessor: NO
customMarkdownProcessor:
useCustomPreprocessor: NO
customPreprocessor:
useFirstH1AsPrintTitle: YES
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 06 Mar, 2022 08:55 PM
You're using the MultiMarkdown processor which requires newlines before headings. Quite a few processors do, really, so the universal solution is to always include a newline before a header.
- Brett