We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For some reason reveal-hugo and org-mode don't work too well together at the moment. This is unexpected, they should work quite well out of the box.
Here is a minimal example of a presentation that does behave as expected (put it into _index.org) :
_index.org
#+OUTPUTS[]: Reveal #+TITLE: works first slide ----- second slide ----- third slide
As five dashes will create a horizontal rule in orgmode this will get you three rather uninteresting slides in reveal-hugo.
But using headlines somehow breaks this (headlines in org are just as in markdown, but with * instead of #).
*
#
#+OUTPUTS[]: Reveal #+TITLE: broken * first slide ----- * second slide ----- * third slide
For some reason this gives me a perfectly normal first slide and an empty second slide (and no third slide).
I
This is a concrete manifestation of the problems mentioned in #72 .
The text was updated successfully, but these errors were encountered:
No branches or pull requests
For some reason reveal-hugo and org-mode don't work too well together at the moment. This is unexpected, they should work quite well out of the box.
Here is a minimal example of a presentation that does behave as expected (put it into
_index.org
) :As five dashes will create a horizontal rule in orgmode this will get you three rather uninteresting slides in reveal-hugo.
But using headlines somehow breaks this (headlines in org are just as in markdown, but with
*
instead of#
).For some reason this gives me a perfectly normal first slide and an empty second slide (and no third slide).
I
This is a concrete manifestation of the problems mentioned in #72 .
The text was updated successfully, but these errors were encountered: