From: Bastien DUMONT <bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: footnote definitons: bug (?) with exclamation mark
Date: Wed, 15 Dec 2021 09:42:37 +0000 [thread overview]
Message-ID: <Ybm4jdGectM5s2S9@localhost> (raw)
In-Reply-To: <574ba8e2f7094f00b7c1c7c92264655d-NSENcxR/0n0@public.gmane.org>
In case it helps debugging, this problem does not appear with pandoc 2.14.1.
Le Wednesday 15 December 2021 à 08:55:55AM, denis.maier-NSENcxR/0n0@public.gmane.org a écrit :
> Hi,
>
>
>
> consider this MWE:
>
>
>
> ```
>
> Test.[^1]
>
>
>
> Test![^2]
>
>
>
> Test!^[asdf]
>
>
>
> [^1]: asdf
>
>
>
> [^2]: asdf
>
> ```
>
>
>
> Running pandoc on this example gives me this error/warning:
>
> [WARNING] Note with key '2' defined at exclamation-bug.md line 7 column 1 but
> not used.
>
>
>
> I’m on pandoc 2.16.2
>
>
>
> Is it possible that the exclamation mark breaks the footnote definition? An
> inline footnote works just fine here.
>
>
>
> Denis
>
> --
> 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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit [2]https://groups.google.com/d/msgid/
> pandoc-discuss/574ba8e2f7094f00b7c1c7c92264655d%40unibe.ch.
>
> References:
>
> [1] mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [2] https://groups.google.com/d/msgid/pandoc-discuss/574ba8e2f7094f00b7c1c7c92264655d%40unibe.ch?utm_medium=email&utm_source=footer
--
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/Ybm4jdGectM5s2S9%40localhost.
next prev parent reply other threads:[~2021-12-15 9:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AdfxkP96Pm83XoPlS5aoEwhbUBmSgw==>
2021-12-15 8:55 ` denis.maier-NSENcxR/0n0
[not found] ` <574ba8e2f7094f00b7c1c7c92264655d-NSENcxR/0n0@public.gmane.org>
2021-12-15 9:42 ` Bastien DUMONT [this message]
2021-12-15 10:57 ` jcr
2021-12-15 15:30 ` John MacFarlane
[not found] ` <m25yrp997o.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
2021-12-17 8:42 ` AW: " denis.maier-NSENcxR/0n0
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=Ybm4jdGectM5s2S9@localhost \
--to=bastien.dumont-vwifzpto/vqstnjn9+bgxg@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).