From: Rainer M Krug <Rainer@krugs.de>
To: Grant Rettke <gcr@wisdomandwonder.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
Johannes Rainer <johannes.rainer@gmail.com>
Subject: Re: Difference between eval and export
Date: Fri, 26 Sep 2014 20:44:52 +0200 [thread overview]
Message-ID: <m2eguyql0b.fsf@krugs.de> (raw)
In-Reply-To: <CAAjq1mcX8=7GDq8J4K3kHnNVfE4gnAcpmq5PHU_5MdhDrMvKxg@mail.gmail.com> (Grant Rettke's message of "Fri, 26 Sep 2014 08:20:00 -0500")
[-- Attachment #1: Type: text/plain, Size: 1859 bytes --]
Grant Rettke <gcr@wisdomandwonder.com> writes:
> My eye is on you post about that topic because I would also like to know.
As you are using R, and if you are using sessions, what about setting
them from within R[1]?
Rainer
>
>
>
> On Fri, Sep 26, 2014 at 8:17 AM, Johannes Rainer
> <johannes.rainer@gmail.com> wrote:
>> thanks Grant for this information.
>>
>> I was just wondering, because it seemed to me that some environment
>> variables (from the shell) are present in the, while they some
>> (LC_ALL) are not present in the export process.
>> In my case, the export call fails with an error message, while there
>> is no problem if I evaluate source block per source block from the
>> buffer.
>>
>> At present I am therefore looking for a way to specify environment
>> variables in the export process, but I have no idea how to do
>> that...
>>
>> On 26 Sep 2014, at 15:11, Grant Rettke <gcr@wisdomandwonder.com> wrote:
>>
>>> On Fri, Sep 26, 2014 at 5:43 AM, Johannes Rainer
>>> <johannes.rainer@gmail.com> wrote:
>>>> I am wondering what the difference between the eval of a source block and the export of a buffer is in terms
>>>> of the process in which the code is evaluated.
>>>
>>> When you evaluate a source block, it executes in the processed defined
>>> by your configuration. Then the results of that evaluation are stored
>>> according to your configuration. For example store the results in an
>>> example block.
>>>
>>> Exporting is the conversion for the org file content into and file
>>> format. During that process, you can configure whether or not you want
>>> evaluation of source blocks to occur during that process.
>>
Footnotes:
[1] http://stat.ethz.ch/R-manual/R-devel/library/base/html/Sys.setenv.html
--
Rainer M. Krug
email: Rainer<at>krugs<dot>de
PGP: 0x0F52F982
[-- Attachment #2: Type: application/pgp-signature, Size: 494 bytes --]
next prev parent reply other threads:[~2014-09-26 18:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 10:43 Difference between eval and export Johannes Rainer
[not found] ` <CAAjq1meS893n_=kZEaFWDKjX_PmJnF82k+8bFZXE-g0+so6LRQ@mail.gmail.com>
2014-09-26 13:17 ` Johannes Rainer
2014-09-26 13:20 ` Grant Rettke
2014-09-26 18:44 ` Rainer M Krug [this message]
2014-09-26 19:58 ` Grant Rettke
2014-09-29 11:14 ` Johannes Rainer
2014-09-29 23:32 ` Grant Rettke
2014-09-30 6:12 ` Johannes Rainer
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=m2eguyql0b.fsf@krugs.de \
--to=rainer@krugs.de \
--cc=emacs-orgmode@gnu.org \
--cc=gcr@wisdomandwonder.com \
--cc=johannes.rainer@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).