I highly recommend ?source.
You can use source("clipboard") on windows, but creating complete files that
define functions and feeding those complete files to source is a significant
step in developing reproducible analyses. Whenever you find yourself pasting
more than a couple of lines (one or two function calls) you should be making
another function. However, even if you resist making functions you should be
making a habit of sourcing complete files from disk rather than passing large
chunks of code.
---------------------------------------------------------------------------
Jeff Newmiller The ..... ..... Go Live...
DCN:<jdnew...@dcn.davis.ca.us> Basics: ##.#. ##.#. Live Go...
Live: OO#.. Dead: OO#.. Playing
Research Engineer (Solar/Batteries O.O#. #.O#. with
/Software/Embedded Controllers) .OO#. .OO#. rocks...1k
---------------------------------------------------------------------------
Sent from my phone. Please excuse my brevity.
On October 29, 2015 8:16:17 AM MST, Victor Tian <tianx...@gmail.com> wrote:
>Hi there,
>
>Often times, I would run R in the terminal when the task is
>computationally
>intensive and a nice-looking UI is less desired.
>
>However, pasting a large chunk of code into the terminal often times
>ends
>up being messed up. In Python, the same problem would happen, however,
>iPython provides a small functionality called magic word such as %paste
>that can help paste the code neatly into the terminal.
>
>I'm wondering if there's a similar functionality in R.
>
>Thanks,
______________________________________________
R-help@r-project.org mailing list -- To UNSUBSCRIBE and more, see
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.
