referenced images in markdown file, cause Marked 2 to double "[]"
// Please enter a detailed description of the issue
// Description of the issue:
In a markdown files I have inserted links to images in the following format:
""
In Marked 2 all such references are reproduced as
“![][](pictures/System%20preferences%20-%20sharing.jpg)"
The image is not shown.
// Please enter a list of steps required to reproduce the issue
// Steps to reproduce:
1. Open Markdown file in MultiMarkdown Composer/Byword
2. Preview within these apps displays the images
3. But preview from nvALt, MultiMarkdown composer etc causes the issue described above.
// If applicable please attach a sample document that causes the issue for you.
// Configuration (do not edit)
Marked 2 925 (Direct)
OS X Version: 10.12.2
---
additionalMathJaxConfig:
allowPageBreakInCode: 1
bookTxtIsLeanpub: 0
codeIsPoetry: 0
collapsibleHeadlines: 0
convertGithubCheckboxes: 1
convertYAMLToMMD: 0
defaultMathJaxConfig: TeX-AMS-MML_HTMLorMML
defaultPreviewStyle: 0
defaultProcessor: MultiMarkdown
enableMiniMap: 1
excludeBlockQuotesFromCounts: 0
excludeFootnotesFromCounts: 0
excludeVerbatimFromCounts: 0
excludeCaptionsFromCounts: 0
folderPreviewExtensionsArray: md, markdown, txt, mdown, html, opml
githubNewlines: 1
h1IsPageBreak: 0
h2IsPageBreak: 0
hrIsPageBreak: 0
includeMathJax: 0
limitTextWidth: 0
minimalJavaScript: 0
outlineModeExtensions:
permissionGranted: 0
printHeaderBottomLeft:
printHeaderBottomRight:
printHeaderFooterFirstPage: 0
printHeaderTopLeft:
printHeaderTopRight:
processHTMLFiles: 1
removeMetadataForPreview: 0
removeYAMLHeaders: 0
scrollToEdit: 1
shouldDetectCritic: 1
shouldHighlightMarkupErrors: 0
shouldLoadCritic: 0
syntaxHighlight: 1
- setup.md 1.2 KB
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 19 Dec, 2016 06:25 PM
This should be corrected in the next update. It's the result of a change
I made to allow processing of relative paths (any not beginning with a
~, /, or protocol) from within included files, but I made an error in
how it replaces the original text.
-Brett
2 Posted by Victor Warner on 20 Dec, 2016 02:46 PM
Brett,
Thank you for the explanation, and I look forward to the next update...
3 Posted by Jeremy on 10 Aug, 2017 08:51 PM
This is still an issue. Is there a fix coming or is there a workaround. I really need adequate image support.
Support Staff 4 Posted by Brett on 12 Aug, 2017 01:02 PM
There's definitely a fix, and coming soon. Sorry the updated got delayed
while I fixed a few other bugs, but I have a beta about to go out for a
quick round of testing then release.
--
Brett Terpstra