From: "Eric Schulte" <schulte.eric@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Re: org-babel-R export parameters
Date: Mon, 07 Jun 2010 12:44:43 -0700 [thread overview]
Message-ID: <87eigilj9w.fsf@gmail.com> (raw)
In-Reply-To: <20100607185119.GG13859@thinkpad.adamsinfoserv.com> (Russell Adams's message of "Mon, 7 Jun 2010 13:51:19 -0500")
Hi Russel,
Russell Adams <RLAdams@AdamsInfoServ.Com> writes:
[...]
>
> So my current issue is that it appears that even though I set :export
> none, the png is still included in my Latex output.
>
> Suggestions?
>
The png is still included your output because the link to the png is
part of your org-mode buffer.
>
> #+results:
> [[file:MyFile.png]]
>
Currently org-babel isn't bold enough to remove existing results during
export. The :exports none argument simply means that babel will not run
the source-code block on export.
I personally find this useful because it allows me to use code blocks to
generate results, and then when I'm content with the file I can set
":exports none" to avoid re-generating the file on every export -- while
retaining the existing link keeps the file included in my export.
I do see how this could be confusing, and maybe it would be appropriate
to begin stripping out the results of code blocks on export.
Best -- Eric
next prev parent reply other threads:[~2010-06-07 19:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-06 22:58 org-babel-R export parameters Russell Adams
2010-06-06 23:27 ` Dan Davison
2010-06-07 8:04 ` Russell Adams
2010-06-07 9:03 ` Dan Davison
2010-06-07 10:31 ` Russell Adams
2010-06-07 18:40 ` Erik Iverson
2010-06-07 18:51 ` Russell Adams
2010-06-07 19:44 ` Eric Schulte [this message]
2010-06-07 19:56 ` Erik Iverson
2010-06-07 22:28 ` Eric Schulte
2010-06-07 20:21 ` Russell Adams
2010-06-07 13:36 ` Erik Iverson
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=87eigilj9w.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--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).