From: "jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <jmuccigr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: pandoc and revealjs r-fit-text and r-stretch?
Date: Fri, 7 Jan 2022 07:32:16 -0800 (PST) [thread overview]
Message-ID: <96ebec32-6e13-49f2-9fe9-bbcfbb74f47bn@googlegroups.com> (raw)
In-Reply-To: <dffcab84-b283-2864-da6d-787851b6a3c3-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1465 bytes --]
Thanks for bringing this up. I have a long-running battle with reveal to
get images to display how I want them too (mainly taking up as much space
as possible without being distorted since I use it for lecture slides).
Going to play with this a bit.
On Wednesday, 5 January 2022 at 16:06:26 UTC-5 Joseph wrote:
> I'd love to use revealjs's `r-fit-text` and `r-stretch` [1] in the new
> year, but they don't work with decks generated by pandoc.
>
> `r-fit-text` doesn't work because pandoc applies the class to both the
> heading and the section, and so the element gets a double dose of movement
> [2].
>
> And an `img.r-stretch` must be a child of the section, and pandoc
> typically puts img in another element (e.g., `p`).
>
> Does anyone have any hacks for using these? Or, if this pandoc generated
> structure isn't likely to change, perhaps we should put a request in to
> Hakim to accommodate the pandoc structure?
>
> [1]: https://revealjs.com/layout/#fit-text
> [2]: https://github.com/jgm/pandoc/issues/5965#issuecomment-862314880
>
--
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/96ebec32-6e13-49f2-9fe9-bbcfbb74f47bn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2599 bytes --]
next prev parent reply other threads:[~2022-01-07 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 21:06 Joseph Reagle
[not found] ` <dffcab84-b283-2864-da6d-787851b6a3c3-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2022-01-06 23:14 ` John MacFarlane
2022-01-07 15:32 ` jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org [this message]
[not found] ` <96ebec32-6e13-49f2-9fe9-bbcfbb74f47bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-01-07 15:57 ` Joseph Reagle
[not found] ` <7c4377d5-12cf-c663-2d48-835dc20de890-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2022-01-07 16:50 ` jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
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=96ebec32-6e13-49f2-9fe9-bbcfbb74f47bn@googlegroups.com \
--to=jmuccigr-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).