From: Rainer M Krug <r.m.krug@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [BABEL] evaluation of R code in export
Date: Thu, 29 Jul 2010 09:15:22 +0200 [thread overview]
Message-ID: <4C512A8A.5030305@gmail.com> (raw)
In-Reply-To: <87iq3z63e3.fsf@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 28/07/10 15:53, Eric Schulte wrote:
> Rainer M Krug <r.m.krug@gmail.com> writes:
>
>> Hi Eric,
>>
>> On 23/07/2010 19:45, Eric Schulte wrote:
>>> Hi Rainer,
>>>
>>> I general it is useful to have the results of Babel-evaluated code
>>> appear in the session history as it can help for debugging.
>>
>> Ok - agreed. The results are quite useful - but I would prefer the
>> history of the commands in the R session which is accessible by C-up to
>> not include the commands issued - but I can live with it as it is now.
>>
>
Hi Eric
> Hi Rainer,
>
> I have found no good answer for sending commands to an inferior process
> w/o adding them to the history ring. There is one possible way forward,
> the investigation of which is now on the task stack for babel
> development but probably won't happen in the near future.
ESS is doing it, when submitting and evaluating a line of R code - maybe
that could help? but as I said before, I don't know anything about
emacs-lisp, and less about how emacs and the modes work, so it might not
be applicable.
As I said - I can easily live with that.
Cheers,
Rainer
>
> Best -- Eric
- --
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)
Centre of Excellence for Invasion Biology
Natural Sciences Building
Office Suite 2039
Stellenbosch University
Main Campus, Merriman Avenue
Stellenbosch
South Africa
Tel: +33 - (0)9 53 10 27 44
Cell: +27 - (0)8 39 47 90 42
Fax (SA): +27 - (0)8 65 16 27 82
Fax (D) : +49 - (0)3 21 21 25 22 44
Fax (FR): +33 - (0)9 58 10 27 44
email: Rainer@krugs.de
Skype: RMkrug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkxRKocACgkQoYgNqgF2egoezwCfQ9Z9YXYV+zbEJZltK4P8mBnQ
9KYAn2dKyN20IzfgeNCqpzc0uyJc72sw
=Qyn2
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2010-07-29 7:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 8:19 [BABEL] evaluation of R code in export Rainer M Krug
2010-07-23 17:45 ` Eric Schulte
2010-07-26 7:53 ` Rainer M Krug
2010-07-28 13:53 ` Eric Schulte
2010-07-29 7:15 ` Rainer M Krug [this message]
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=4C512A8A.5030305@gmail.com \
--to=r.m.krug@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@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).