From: John Hendy <jw.hendy@gmail.com>
To: Charles Berry <ccberry@ucsd.edu>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Proposal/request for input: slidify export for html slides
Date: Fri, 7 Feb 2014 23:51:55 -0600 [thread overview]
Message-ID: <CA+M2ft-w4z1TogJ2+nD55iMTXqObfJz4_DbYmsLHRnKAUE-zeA@mail.gmail.com> (raw)
In-Reply-To: <CA+M2ft_mZtwvTpScZ=hQX50_dKQicxnmn0AWNYVarzodeMW7qQ@mail.gmail.com>
On Fri, Feb 7, 2014 at 11:38 PM, John Hendy <jw.hendy@gmail.com> wrote:
> On Fri, Feb 7, 2014 at 7:04 PM, Charles Berry <ccberry@ucsd.edu> wrote:
[snip]
> I'll look into those. I just cloned your repo and loaded ox-ravel.
> Quite nice! It worked /pretty/ well out of the box. One issue is that
> it doesn't seem to obey :eval no for babel blocks. I exported to .Rmd
> successfully, but the presentation has a bunch of errors in the code
> blocks from trying to actually execute the code. The .Rmd doesn't have
> any instances of ```{r eval=F}; could this feature be added?
Just kidding. Discovered #+attr_ravel and the proper knitr argument
for code chunks, which worked as expected with:
#+attr_ravel: eval=F
#+begin_src R ...
I still think it makes sense to allow :eval no. This seems more
"Org-ish" since the ideology is to have one set of Org syntax where
possible, which translates to any number of languages. I get that we
have #+attr_latex for latex-only things, #+attr_html for html-only
things, and so on, but I wouldn't consider :eval to fall into this
category. Or perhaps I don't understand... would the idea be that I
don't want to run it in *Org*, but I'd not want all my chunks disabled
in the .Rmd?
My workflow might be odd in that I tend to futz with plot parameters
once, get the desired image, and then set :eval no for the rest of my
document work so I don't have to wait for plots on iterative exports.
I try to put all my setup code (load packages, data
reading/manipulation, etc.) in it's own block so that I can easily run
that whenever I first open the document. From there I only need to
re-run a plot block if necessary and I'll just temporarily change
:eval no -> yes and then back again after execution.
Thanks again,
John
next prev parent reply other threads:[~2014-02-08 5:51 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
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 [this message]
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=CA+M2ft-w4z1TogJ2+nD55iMTXqObfJz4_DbYmsLHRnKAUE-zeA@mail.gmail.com \
--to=jw.hendy@gmail.com \
--cc=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).