[R] R editor vs. Tinn-R
Thierry.ONKELINX at inbo.be
Fri Jan 12 21:06:42 CET 2007
Instead of discussing this odd behaviour of TINN-R, I would prefer a discussion on importing data through the clipboard. In my opinion it isn't a good a idea to import data with the clipboard. I know that it's a quick and dirty way to get your data fast into R.
But I see two major drawbacks. First of all you have no chance of checking what data you imported. This is important when you need to check your results a few days (weeks, months or even years) later. A second drawback is that you won't feel the need to store your data in an orderly fashion. Which often leads to a huge pile of junk, instead of a valuable dataset...
Van: r-help-bounces op stat.math.ethz.ch namens BBands
Verzonden: vr 12-1-2007 19:47
Onderwerp: Re: [R] R editor vs. Tinn-R
On 1/12/07, Martin Becker <martin.becker op mx.uni-saarland.de> wrote:
> Depending on which button you press in Tinn-R, the clipboard is used to
> transfer the commands to R, so sometimes you can't rely on the previous
> contents of the clipboard while using Tinn-R. If you use the
> "(source)"-versions of the buttons, the content of the clipboard should
> be preserved.
Something odd is going on. I can confirm that read.delim("clipboard")
works from R, but not from Tinn-R. What seems odd is that the contents
of the clipboard _are_ preserved after the Tinn-R send, so that a
subsequent paste or read.delim("clipboard") from R works correctly.
Perhaps Tinn-R restores the contents of the clipboard after sending to
R such that the R command runs before the restore takes place?
John Bollinger, CFA, CMT
If you advance far enough, you arrive at the beginning.
R-help op stat.math.ethz.ch mailing list
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
More information about the R-help