From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Joseph Reagle
<joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: comments in headings messing up attribtues
Date: Mon, 07 Jun 2021 08:05:02 -0600 [thread overview]
Message-ID: <m2mts1wz1t.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <79902156-0bd0-bbf6-d334-3a5ae29fcaff-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
Attributes have to come at the very end.
So, you'd need to put the comment before the attribute.
Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> writes:
> When I have a comment in a heading with an attribute declaration, pandoc seems to take it literally.
>
> https://pandoc.org/try/?text=%23%23+big+text+%7B.r-fit-text%7D+%3C!--+TODO%3A+now+broken+--%3E%0A&from=markdown&to=revealjs&standalone=0
>
> I'm going to try to use `--strip-comments` and see if that works as a short term fix, but is this a bug?
>
> --
> 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/79902156-0bd0-bbf6-d334-3a5ae29fcaff%40reagle.org.
next prev parent reply other threads:[~2021-06-07 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 19:35 Joseph Reagle
[not found] ` <79902156-0bd0-bbf6-d334-3a5ae29fcaff-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2021-06-07 13:34 ` Joseph Reagle
2021-06-07 14:05 ` John MacFarlane [this message]
[not found] ` <m2mts1wz1t.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2021-06-07 14:34 ` Joseph Reagle
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=m2mts1wz1t.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=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).