From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: revealjs' "data-auto-animate" not passing through?
Date: Wed, 4 Oct 2023 11:26:15 -0700 [thread overview]
Message-ID: <94F47580-8DEF-4F67-90C6-720190E13631@gmail.com> (raw)
In-Reply-To: <875872a0-d638-4c4c-a4e4-fa4b09262d13-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
Pandoc is putting the attribute on the h2, but it needs to be moved to the encompassing section, presumably. Maybe put up an issue about this?
> On Oct 4, 2023, at 5:45 AM, Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> wrote:
>
> Has anyone use data-auto-animate in their markdown-2-reveals conversions. The following doesn't work. First, I'm setting `data-auto-animate` to true so it's seen as an attribute. Neither of the following work as I'd expect.
>
> ```
> ## Auto-animate {data-auto-animate=true}
>
> ## Auto-animated {data-auto-animate=true style="margin-top: 10px; color: red;"}
>
>
> ## {data-auto-animate=true}
>
> Auto-animate
>
> ## {data-auto-animate=true}
>
> [Auto-animated]{style="margin-top: 100px; color: red;"}
>
>
> ```
>
> --
> 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/875872a0-d638-4c4c-a4e4-fa4b09262d13%40reagle.org.
next prev parent reply other threads:[~2023-10-04 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 12:45 Joseph Reagle
[not found] ` <875872a0-d638-4c4c-a4e4-fa4b09262d13-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2023-10-04 18:26 ` John MacFarlane [this message]
[not found] ` <94F47580-8DEF-4F67-90C6-720190E13631-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-10-05 12:53 ` 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=94F47580-8DEF-4F67-90C6-720190E13631@gmail.com \
--to=fiddlosopher-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).