From: John Hendy <jw.hendy@gmail.com>
To: Ken Mankoff <mankoff@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: exporting documents w/ babel results w/o evaluating babel blocks
Date: Fri, 20 May 2016 11:14:48 -0500 [thread overview]
Message-ID: <CA+M2ft8GncMc0NYTvcmieBmPW7OWHA_taqmNkZLwAEKeHcvMPw@mail.gmail.com> (raw)
In-Reply-To: <m2y474raby.fsf@client-75-102-66-133.mobility.psu.edu>
On Fri, May 20, 2016 at 10:57 AM, Ken Mankoff <mankoff@gmail.com> wrote:
> Hi List,
>
> I'm repeating a question here from a recent bug report because I have a feeling official-looking bug reports might get read less than normal questions. Sorry for the re-post.
>
> As of an Org git commit a few weeks ago, Org exporting (and therefore Org) has become basically unusable for me. I used to be able to export code block results without evaluating the block during the export. I can no longer do this.
>
> The following headers used to support the above behavior:
>
> #+BEGIN_SRC python :exports results :results output
> #+BEGIN_SRC python :exports results :results file
> (and possibly with ":session foo" also)
Well, you're exporting them at least *once*, right? If not, where are
the results coming from?
Perhaps my use case is similar. I often write up an org doc with a
pretty heavy setup heading containing my main data reading in,
manipulation, statistics, etc. Maybe up to 100k total rows in a data
frame in R. Once I run that block the first time I'm working on the
document I just put =:eval no= in the src block options.
I do the same as I'm tweaking plots. Every code block I create has
:eval yes initially and once I'm satisfied with the results I just
change to :eval no and the generated results (for me, typically a
#+results line containing a link to a pdf plot generated by my code
block) are still included.
Does this help at all? Sorry if I'm not understanding
>
> Is anyone running the current git head? And if so, can you export a document that consists of the following, or something similar to the following (i.e. do you use ":cache t" or ":cache nil")?
>
> #+BEGIN_SRC python :results output :exports results :session foo
> print("hello, world")
> #+END_SRC
> #+RESULTS:
> : hello, world
>
> If you can export this without running the code, what settings are you using? In particular, what is the value of =org-export-babel-evaluate=?
Mine is set to t. Interestingly, when I export the above after
deleting the results bit, no new results are generated. When I C-c
C-c, they are replaced. When I add :eval no, it does't appear to run
the code.
Hope that helps,
John
>
> Thanks,
>
> -k.
>
next prev parent reply other threads:[~2016-05-20 16:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 15:57 exporting documents w/ babel results w/o evaluating babel blocks Ken Mankoff
2016-05-20 16:14 ` John Hendy [this message]
2016-05-20 16:45 ` Ken Mankoff
2016-05-20 17:25 ` John Hendy
[not found] ` <878addc2b6b14ce99e907921f0985d24@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-05-20 16:59 ` Eric S Fraga
2016-05-20 17:06 ` Ken Mankoff
[not found] ` <b29fde01938940d3b115abd9b257dc57@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-05-20 17:11 ` Eric S Fraga
2016-05-20 17:23 ` John Hendy
2016-05-20 17:38 ` Ken Mankoff
2016-05-20 17:32 ` Ken Mankoff
2016-05-20 18:46 ` Nick Dokos
2016-05-20 21:20 ` Charles C. Berry
2016-05-21 19:01 ` Nick Dokos
2016-05-22 19:58 ` John Hendy
2016-05-22 21:52 ` Charles C. Berry
2016-05-23 18:27 ` Nick Dokos
2016-05-23 18:34 ` John Hendy
2016-05-23 20:08 ` Charles C. Berry
2016-05-24 1:34 ` Grant Rettke
2016-05-24 10:17 ` Andreas Kiermeier
2016-05-24 14:32 ` Ista Zahn
2016-05-24 15:09 ` Anthony Cowley
2016-05-24 15:48 ` Charles C. Berry
2016-05-24 15:53 ` Charles C. Berry
2016-05-20 23:06 ` Ken Mankoff
[not found] <0e207e1cbcc44453b29eea98ca5ebe05@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-05-20 16:13 ` Eric S Fraga
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+M2ft8GncMc0NYTvcmieBmPW7OWHA_taqmNkZLwAEKeHcvMPw@mail.gmail.com \
--to=jw.hendy@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mankoff@gmail.com \
/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).