emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Michael Welle <mwe012008@gmx.net>
To: emacs-orgmode@gnu.org
Subject: Re: org-reveal: content side by side
Date: Wed, 07 Feb 2018 18:42:37 +0100	[thread overview]
Message-ID: <87372chf1u.fsf@luisa.c0t0d0s0.de> (raw)
In-Reply-To: <CAN_Dec-VFAppweiNsHcdUbwgPW7KQf9afC3seWLT45GaE6SHtw@mail.gmail.com> (Matt Price's message of "Mon, 5 Feb 2018 19:37:39 -0500")

Hello,

Matt Price <moptop99@gmail.com> writes:

> for this issue, I define a class "paired" in my local cass file (or
> actually, I now use a very modestly edited custom theme) :
>
>
> .paired {
>     float:left !important;
>     max-width:47% !important;
>
> }
>
> and then in the org file:
> :#+ATTR_HTML: :class paired
>
> That works OK for me. the "!important" is necessary because reveal css is
> prtty greedy & hard to override.
thanks, I will check it out. I have to say it takes quite some time to
get a presentation that looks as good as the beamer based presentation I
use as an example.

The current issue I have is this. I have a structure like this:

* foo
** foo1
** foo2

Basically foo acts as a container for the content. I want foo to appear
in the table of contents and I want two slides, foo1 and foo2, and none
for foo. I'm nearly there, but I don't know how to suppress the
generation of a slide for foo.

I could use this structure:

* foo1
* foo2

But I miss the container that groups the content for me, the presenter.
And what is more important, I don't know how to get foo into the TOC (in
a nice way).

Or I could use:

* foo1
** foo2

Which seems to have even more issues: the content of foo2 is on the same
level as the content of foo1, it's not sub-content. The headers of the
slides have different sizes then, etc.

Regards
hmw

next prev parent reply	other threads:[~2018-02-07 17:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-04 10:59 org-reveal: content side by side Michael Welle
2018-02-04 18:46 ` Michael Welle
2018-02-06  0:37   ` Matt Price
2018-02-07 17:42     ` Michael Welle [this message]
2018-02-11 15:29 ` Michael Welle
2018-02-13 11:19   ` Eric S Fraga
2018-02-13 11:43     ` Michael Welle
2018-02-13 12:33   ` Jens Lechtenboerger
2018-02-13 15:16     ` Michael Welle
2018-02-13 16:16       ` Jens Lechtenboerger
2018-02-13 16:21       ` Michael Welle

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87372chf1u.fsf@luisa.c0t0d0s0.de \
    --to=mwe012008@gmx.net \
    --cc=emacs-orgmode@gnu.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

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).