Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ignore non-recognized markdown contents #1455

Closed
soubinan opened this issue Jun 30, 2024 · 3 comments · Fixed by stateful/runme#627
Closed

Ignore non-recognized markdown contents #1455

soubinan opened this issue Jun 30, 2024 · 3 comments · Fixed by stateful/runme#627
Assignees

Comments

@soubinan
Copy link

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:

image

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
+++
@sourishkrout
Copy link
Member

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.

@sourishkrout
Copy link
Member

@soubinan this is fixed as of v3.6.2 (just updated to latest in the vscode). Lemme me know how it goes please.

@soubinan
Copy link
Author

soubinan commented Jul 11, 2024

Cool! It works as expected!
Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants