On Thu, 20-Aug-2009 at 12:21AM +0100, Ted Harding wrote: [....]
|> Again, what I routinely do (in Linux) when developing R code is to |> have two terminal windows open. In one I am running R. In the |> other, beside it, I am editing a file of R code. To run code in R |> that has been entered in the "code" window, I just highlight it |> with the mouse in the "code" window, and then paste it into the "R" |> window. It's even easier using ESS -- highlight in your "code" buffer, press your designated function key and the code will be run in the *R* buffer -- or you can use another function key to run code line by line, or, etc. etc. I must admit I didn't like Emacs for the first week or so but when I saw how easy it was to manage code, I decided it was worth the effort to get used to the strange old paradigm which had been developed before the invention of the mouse. I'd also admit that I've seen people do things amazingly quickly using vi -- despite its strange jumping from command mode to insert mode. As others have indicated, whatever you use, it makes good sense to keep a file of the code that you use. Rerunning is something I do as a rule, not an exception. It's particularly useful when follow up work arrives which can reuse the same code or a slightly modified version of it. [...] -- ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~. ___ Patrick Connolly {~._.~} Great minds discuss ideas _( Y )_ Average minds discuss events (:_~*~_:) Small minds discuss people (_)-(_) ..... Eleanor Roosevelt ~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~. ______________________________________________ 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.