Mike,
There are several options to pursue, depending on your answer
to the question:
Why are you staying within the Rgui if you are already an
Emacs ESS user?
1. If you don't need any other feature of Rgui on Windows,
then don't use it. From emacs, enter
M-x R
and you will immediately be inside the *R* buffer running R.
All emacs features immediately work the way you expect them to work.
2. If you need another feature of Rgui (and I know of one: rcom and
Rgui work together smoothly, rcom and *R* are not comfortable
together), then try the experimental ESS command
M-x Rgui
that I added to ESS in March 2008.
Full documentation of M-x Rgui is part of the ESS distribution in file
.../ess/doc/rgui-doc.txt
The specific request for live history from the Rgui is in principle
easy to design in this setting. Here are the steps:
1. Send to Rgui the command
history()
and redirect the response to a file.
2. Open the file in emacs.
3. Pick your specific command to send back or to edit.
4. Send revised command back to Rgui, and close history file.
It shouldn't be too hard to put this sequence on a function key.
Let me know if the design does what you want.
Rich
______________________________________________
R-help@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
