Re: [R] communicate from Rterm

2008-01-11 Thread Prof Brian Ripley
; ">" "out.txt" >>> >> >> it restores the correct workspace, but then it fails to source the >> script, which is located in the same dir as the workspace. >> >> inside R >> >>> source("m.in.R") # does the job, so

Re: [R] communicate from Rterm

2008-01-11 Thread Duncan Murdoch
e job, so it is not a finding problem > > BTW is it possible to get the error message from R somehow??? > > > Original Message > From: [EMAIL PROTECTED] > Date: 01/11/2008 6:30 > To: "stephen bond"<[EMAIL PROTECTED]> > Cc: > Subj: Re: [R] commun

Re: [R] communicate from Rterm

2008-01-11 Thread stephen bond
message from R somehow??? Original Message---- From: [EMAIL PROTECTED] Date: 01/11/2008 6:30 To: "stephen bond"<[EMAIL PROTECTED]> Cc: Subj: Re: [R] communicate from Rterm On 1/11/2008 9:18 AM, stephen bond wrote: > Please, help with announcing an error from Rterm: >

Re: [R] communicate from Rterm

2008-01-11 Thread Duncan Murdoch
On 1/11/2008 9:18 AM, stephen bond wrote: > Please, help with announcing an error from Rterm: > > I am calling R from an Excel VBA and noticed that if there is an error > nothing conspicuous happens. I would like just a popup window when R > cannot finish cleanly. The "ret " value returned from

[R] communicate from Rterm

2008-01-11 Thread stephen bond
Please, help with announcing an error from Rterm: I am calling R from an Excel VBA and noticed that if there is an error nothing conspicuous happens. I would like just a popup window when R cannot finish cleanly. The "ret " value returned from Shell is useless in determining what happened. Tha