From: Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: pandoc as a linkchecker?
Date: Mon, 14 Sep 2020 09:19:38 -0400 [thread overview]
Message-ID: <c5259326-1317-e43a-6416-25922630b25e@reagle.org> (raw)
In-Reply-To: <CADAJKhCpmA-g_LPufFmZxSY2dVJzYGw_S8vvsPrK2YQoHpRNNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 9/12/20 4:31 PM, BPJ wrote:
> There are tools which check links in HTML, so one option would be to convert your Markdown files to HTML and then check the links in there.
Yes, that's what I did for a while. This semester, I'm using `pytest-check-links` which can operate on markdown files, though it internally converts to HTML first, and so would not be able to provide line numbers [1]. However, I thought it might be possible to provide line numbers eventually given John's comment in #4565, "The commonmark parser in commonmark-hs, which I'll be integrating into pandoc, already has complete source position information." [2] (I could be completely misunderstanding what this means.)
[1]: https://github.com/jupyterlab/pytest-check-links/issues/23
[2]: https://github.com/jgm/pandoc/issues/4565
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/c5259326-1317-e43a-6416-25922630b25e%40reagle.org.
next prev parent reply other threads:[~2020-09-14 13:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 19:12 Joseph Reagle
[not found] ` <f87a3346-3243-0cd4-a101-107e5ffe4902-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2020-09-12 19:35 ` Gwern Branwen
2020-09-12 19:38 ` Daniel Staal
2020-09-12 20:19 ` Albert Krewinkel
2020-09-12 20:31 ` BPJ
[not found] ` <CADAJKhCpmA-g_LPufFmZxSY2dVJzYGw_S8vvsPrK2YQoHpRNNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-09-14 13:19 ` Joseph Reagle [this message]
[not found] ` <c5259326-1317-e43a-6416-25922630b25e-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2020-09-14 13:23 ` Gwern Branwen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c5259326-1317-e43a-6416-25922630b25e@reagle.org \
--to=joseph.2011-t1oy19wchswdnm+yrofe0a@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).