From: Charles Berry <ccberry@ucsd.edu>
To: emacs-orgmode@gnu.org
Subject: Re: Proposal/request for input: slidify export for html slides
Date: Fri, 7 Feb 2014 21:50:11 +0000 (UTC) [thread overview]
Message-ID: <loom.20140207T202459-501@post.gmane.org> (raw)
In-Reply-To: CA+M2ft8uUfbG_6u+ERx195kL1YnrrA-5P_vrRs3C6oseqOos-Q@mail.gmail.com
John Hendy <jw.hendy <at> gmail.com> writes:
>
> An interesting update on this. Aside from some image and code block
> stuff, the following works surprisingly well!
> - Export Org -> markdown (md)
> - Start an R session and `setwd("/path/to/file.md")`
> - Run `library(slidify)` and `author("deck")
> - Copy the deck/assets folder into the parent directory
> - Copy the header code from the resultant deck/index.Rmd file into
> exported .md file
> - Add three hyphens before each heading (headings are # Slide title)
> - Save the file as file.Rmd (vs. file.md)
> - From the R session, do `setwd("../")` (running `author("deck")`
> changes the working directory to deck/
> - Run `slidify("file.Rmd")`
>
[much deleted]
John,
You can put the header code into an MD export block (and ignore index.Rmd).
You can add '#+MD: ---' keyword lines to mark new slides.
Then you export to my.Rmd directly (using ravel) and run slidify("my.Rmd").
Graphics 'just work', but you have to mind the spacing to be sure the slides
render nicely.
The file slidify-example.org at
https://github.com/chasberry/orgmode-accessories/
produces a minimal slidify slideshow with code, computed results, and graphics.
And it has some notes on org --> slidify using the md-knitr backend from
ox-ravel.
Ideally, a `md-slidify' backend would get written to automagically
produce the yaml header, separate slides based on headline levels, et
cetera. But that is a low priority right now.
HTH,
Chuck
next prev parent reply other threads:[~2014-02-07 21:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 0:05 Proposal/request for input: slidify export for html slides John Hendy
2014-01-30 0:57 ` Ahmadou Dicko
2014-01-30 1:45 ` Rick Frankel
2014-01-30 4:26 ` John Hendy
2014-02-07 1:26 ` John Hendy
2014-02-07 7:58 ` Andreas Leha
2014-02-07 21:50 ` Charles Berry [this message]
2014-02-07 22:18 ` John Hendy
2014-02-08 1:04 ` Charles Berry
2014-02-08 5:38 ` John Hendy
2014-02-08 5:51 ` John Hendy
2014-02-08 17:18 ` Charles Berry
2014-02-09 22:26 ` John Hendy
2014-02-10 4:16 ` Charles Berry
2014-02-10 4:54 ` John Hendy
2014-02-08 9:33 ` Nicolas Goaziou
2014-02-08 14:11 ` John Hendy
2014-02-08 14:52 ` Nicolas Goaziou
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=loom.20140207T202459-501@post.gmane.org \
--to=ccberry@ucsd.edu \
--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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).