Addition of an --ignore-errors
flag
#9858
mortonmills
started this conversation in
Ideas
Replies: 2 comments 1 reply
-
In general, errors are throws if there is no reasonable way to continue with the execution. Specific cases where a warning might suffice should be looked at individually. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I also would like to have $ pandoc gfm.md -s -t typst -o gfm.pdf
error: file not found (searched at /home/user/Markup/1/home/user/Images/Misc/240px-Instagram_icon.png)
┌─ toPdfViaTempFile100364-0.html:356:11
│
356 │ #box(image("/home/user/Images/Misc/240px-Instagram_icon.png"))
│ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Error producing PDF. I didn't care about the error (missing image file), but if I have the flag, don't need to edit the markdown file to get PDF created. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I've been using pandoc to convert repo docs (markdown, pandoc, node, vscode.... ) into html and epubs for offline use.
However, I receive errors in some cases and only receive partial output.
I've searched the pandoc issues and discussions,
#4893 requested this as an option several years ago.
I realize the current solution is to use filters.
However, having an
--ignore-errors
flag would greatly simplify usage when errors are acceptableand could also act as a last resort option in the case filters won't do or are too complex to write.
Beta Was this translation helpful? Give feedback.
All reactions