Pasting a large chunk of R code in terminals
I don't get the impression that you understood the part of my response where I said the feature does exist.
You might find reading ?file helpful, in particular the section titled "Clipboard".
---------------------------------------------------------------------------
Jeff Newmiller The ..... ..... Go Live...
DCN:<jdnewmil at 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 12:26:56 PM MST, Victor Tian <tianxu03 at gmail.com> wrote:
Not a specific problem. Just an issue encountered pasting R codes in terminals from time to time. Cheers, Xu On Thu, Oct 29, 2015 at 2:46 PM, jim holtman <jholtman at gmail.com> wrote:
Another good reason for using "source" instead of copy/paste is that
if an
error occurs, the 'sourced' script will stop at the error, while the copy/paste will keep on chugging away, knowing who does what in the
rest of
the script. Most of the editors I have used on Windows (notepad++,
tinn-r)
support highlighting code and then automatically creating a temporary
file
that is 'sourced' in. Jim Holtman Data Munger Guru What is the problem that you are trying to solve? Tell me what you want to do, not how you want to do it. On Thu, Oct 29, 2015 at 2:13 PM, Victor Tian <tianxu03 at gmail.com>
wrote:
Thanks, Marc and Jeff, for the advice of running a file of R code
rather
than a chunk of R code. Just thought it would be nice to have a feature like this so that
there's
still a sense of interaction in running R code. It was a random idea and I think using "source" would achieve the
same
goal. Thanks, Xu On Thu, Oct 29, 2015 at 11:51 AM, Jeff Newmiller < jdnewmil at dcn.davis.ca.us> wrote:
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:<jdnewmil at 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
<tianxu03 at 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,
--
*Xu Tian*
[[alternative HTML version deleted]]
______________________________________________ R-help at 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.