From: BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: pandoc as a linkchecker?
Date: Sat, 12 Sep 2020 22:31:50 +0200 [thread overview]
Message-ID: <CADAJKhCpmA-g_LPufFmZxSY2dVJzYGw_S8vvsPrK2YQoHpRNNQ@mail.gmail.com> (raw)
In-Reply-To: <f87a3346-3243-0cd4-a101-107e5ffe4902-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]
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.
--
Better --help|less than helpless
Den lör 12 sep. 2020 21:12Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> skrev:
> It's time to check which links in my syllabi are broken, and I'm again
> cursing under my breath that there's no multi-format linkchecker out there
> that can report line numbers. Then I thought, what about my favorite tool!?
>
> Pandoc already chases links for `self-contained`, so I suspect this
> wouldn't be hard. Bonus: could it report the line of a markdown file where
> a broken link is?
>
> --
> 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/f87a3346-3243-0cd4-a101-107e5ffe4902%40reagle.org
> .
>
--
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/CADAJKhCpmA-g_LPufFmZxSY2dVJzYGw_S8vvsPrK2YQoHpRNNQ%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2449 bytes --]
next prev parent reply other threads:[~2020-09-12 20:31 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 [this message]
[not found] ` <CADAJKhCpmA-g_LPufFmZxSY2dVJzYGw_S8vvsPrK2YQoHpRNNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-09-14 13:19 ` Joseph Reagle
[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=CADAJKhCpmA-g_LPufFmZxSY2dVJzYGw_S8vvsPrK2YQoHpRNNQ@mail.gmail.com \
--to=melroch-re5jqeeqqe8avxtiumwx3w@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).