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: Sun, 9 Feb 2014 16:26:18 -0600 [thread overview]
Message-ID: <CA+M2ft8HN1m-sjg5FQoFUjbV4xaKRxyMLCga9STCunTT8+yxtg@mail.gmail.com> (raw)
In-Reply-To: <loom.20140208T173322-912@post.gmane.org>
On Sat, Feb 8, 2014 at 11:18 AM, Charles Berry <ccberry@ucsd.edu> wrote:
>> 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. [...]
>
> In principal, it makes sense to map babel header args to knitr chunk
> options. At least when the headers arg and chunk option do about the
> same thing.
>
> But there is some effort and overhead involved, so only the most
> useful (IMO) have been mapped. Right now, `:noweb yes' will expand the
> reference(s) in place before export, and `:exports none' will not export
> the block. Maybe one day ...
Understood, and no worries. I'm making progress. When you say "expand
references," I'm not sure I follow what that means. References =
references to variables? So something like :var something=something?
> More a matter of what my workflow is (so the issue doesn't arise). I use
> the cache=TRUE chunk option on the knitr side to save the results of long
> running computations. When I start work, I execute a src block that loads
> knitr and knits the *.Rnw (or *.Rmd, etc), which has the side effect of
> loading the cached objects. Then I edit the *.org document. If I am
> working on R code, I run the code interactively either from the src edit
> buffer or I C-c C-c the src block. Its handy to leave the results in the
> *.org buffer for reference - they get stripped on export. Maybe I edit
> a figure caption (knitr option fig.cap=<R character object>), equations,
> or text. When I am ready to see the formatted doc, I export via ravel,
> knit, and view. The cached objects get rebuilt as needed.
Ah. I think I follow this. If you knit the exported .org -> Rmd file
in the same R session that Org is using, if you change the .org and
re-export to .Rmd, knitr is smart enough not to re-run the code? Is
that what you mean? That also must imply that export to .Rmd doesn't
execute any of the Org babel code, right (otherwise there would be no
benefit to your workflow since you'd be waiting for Org anyway)?
If that's the case, I think I could roll with that -- I'd just have
:eval yes if exporting to .Rmd -> knitr, and do a replace-string to
:eval no if I was going to export to Beamer.
>> 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.
>>
>
> Not odd at all if it saves you time.
>
> But if it takes long to rebuild the objects in that first src block, you
> might want to try the cache=TRUE route.
I'm a bit hung up on including non-code-generated images. I'm working
through one of my presentations to convert to slidify (and may write
up a Worg tutorial or just one on my blog to add to collective
knowledge) but am not sure of the right "universal Org syntax" that
will work with multiple backends. I'm most used to something like
this:
#+begin_center
#+attr_backend :height {6cm, 400px, etc.}
[[./path/to/image.png]]
#+end_center
That's not seeming to work with ox-ravel thus far. I'd love not to
have to change the Org image syntax to straight markdown just for my
occasional use of slidify.
Thanks again -- you've been immensely helpful in getting me started!
John
>
>
> Chuck
>
> p.s. the weird fontification you noted one posting up in this thread seems
> like something to raise with the slidify/knitr devs after checking the
> *.Rmd to be sure there is no org/ravel induced problem.
>
Will do, but I'm really thinking it's got to be crud that exported
from my various latex lines/settings. If things persist after making
sure none of that made it through to .Rmd, I'll submit an example file
to either knitr or slidify github issues.
>
>
next prev parent reply other threads:[~2014-02-09 22:26 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
2014-02-08 17:18 ` Charles Berry
2014-02-09 22:26 ` John Hendy [this message]
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+M2ft8HN1m-sjg5FQoFUjbV4xaKRxyMLCga9STCunTT8+yxtg@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).