You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using it for weeks now, and I noticed an annoying issue.
When you have a markdown file with some exotic content (like presentations in Markdown format in instance)
It will be great if RUNME could just ignore them (or raise a notification we can close) and let us read the markdown file anyway (without the RUNME parsing)
Currently, RUNME shows an error instead of showing the file content.
To have a kind of fallback behaviour will be nice, so the non-recognized Markdown format would still be usable in VS Code.
Below, a screenshot to illustrate my experience:
In this example, the Markdown is in a special format for Hugo:
$ cat archetypes/default.md
+++
title = '{{ replace .File.ContentBaseName "-" " " | title }}'
date = {{ .Date }}
draft = true
+++
The text was updated successfully, but these errors were encountered:
Thanks for reporting this issue, @soubinan. Runme's deserializer should indeed be able to ignore+retain the content. We'll look into it. Will keep you posted.
Hi,
Firstly, thank you for this great tool!
I am using it for weeks now, and I noticed an annoying issue.
When you have a markdown file with some exotic content (like presentations in Markdown format in instance)
It will be great if RUNME could just ignore them (or raise a notification we can close) and let us read the markdown file anyway (without the RUNME parsing)
Currently, RUNME shows an error instead of showing the file content.
To have a kind of fallback behaviour will be nice, so the non-recognized Markdown format would still be usable in VS Code.
Below, a screenshot to illustrate my experience:
In this example, the Markdown is in a special format for Hugo:
The text was updated successfully, but these errors were encountered: