Check out ?sprintf, ?cat, ?noquote, ?format, ?formatC, ?print.
Also maybe ?sub, ?gsub, ?chartr, ?grep.
To view the code that prints summary(lm(...whatever...)), put this on
a line by itself:
stats:::print.summary.lm
The summary statement mentioned above outputs an object of
class "summary.lm"
I am using the sink function to save several results (i.e. values of many
different variables) to an output file. However, the output looks unattractive
because it displays line numbers next to each new variable, it is difficult to
remove the R variable name from the output, and I cannot print
On Fri, Apr 15, 2005 at 12:37:46PM -0400, Gabor Grothendieck wrote:
> On 4/15/05, Jan T. Kim <[EMAIL PROTECTED]> wrote:
> > On Fri, Apr 15, 2005 at 11:27:13AM -0400, Gabor Grothendieck wrote:
> > > On 4/15/05, Vivek Rao <[EMAIL PROTECTED]> wrote:
> > > > Many of my R scripts call other R scripts us
On 4/15/05, Jan T. Kim <[EMAIL PROTECTED]> wrote:
> On Fri, Apr 15, 2005 at 11:27:13AM -0400, Gabor Grothendieck wrote:
> > On 4/15/05, Vivek Rao <[EMAIL PROTECTED]> wrote:
> > > Many of my R scripts call other R scripts using the
> > > source function. If there is a syntax error in one of
> > > th
On Fri, Apr 15, 2005 at 11:27:13AM -0400, Gabor Grothendieck wrote:
> On 4/15/05, Vivek Rao <[EMAIL PROTECTED]> wrote:
> > Many of my R scripts call other R scripts using the
> > source function. If there is a syntax error in one of
> > the scripts, I get an error message such as
> >
> > Error in
On 4/15/05, Vivek Rao <[EMAIL PROTECTED]> wrote:
> Many of my R scripts call other R scripts using the
> source function. If there is a syntax error in one of
> the scripts, I get an error message such as
>
> Error in parse(file, n, text, prompt) : syntax error
> on line 1
>
> but the name of the
Many of my R scripts call other R scripts using the
source function. If there is a syntax error in one of
the scripts, I get an error message such as
Error in parse(file, n, text, prompt) : syntax error
on line 1
but the name of the file where the error occurs is not
given. Other error messages s
On Mon, 12 Apr 2004, Tony Plate wrote:
> Isn't source file information often recorded in the "source" attribute on
> functions (or calls)? Could either the execution engine or the debugger
> refer to that information? (Though, in the debugger it might be impossible
> to uniquely identify express
On Mon, 12-Apr-2004 at 03:20PM -0700, Webb Sprague wrote:
|> Hi Patrick,
|>
|> >It's very simple using a browser() line in your function somewhere you
|> >know your code's OK, then run line by line.
|> >
|> The problem is that sometimes you have code of a few hundred lines, to
|> which you hav
Isn't source file information often recorded in the "source" attribute on
functions (or calls)? Could either the execution engine or the debugger
refer to that information? (Though, in the debugger it might be impossible
to uniquely identify expressions that appear multiple times in the functi
On Mon, 12 Apr 2004 15:20:58 -0700, you wrote:
>Hi Patrick,
>
>>It's very simple using a browser() line in your function somewhere you
>>know your code's OK, then run line by line.
>>
>The problem is that sometimes you have code of a few hundred lines, to
>which you have added a strange little
On Tue, 13 Apr 2004, Jason Turner wrote:
> Webb Sprague wrote:
> > I already use ESS. If it would give line numbers, my life would be
> > perfect!
>
> It does, if you don't use source(). Have your R code in one buffer, and
> the R session running, and (from the code buffer), type C-c C-l.
>
Yes
Webb Sprague wrote:
I already use ESS. If it would give line numbers, my life would be
perfect!
It does, if you don't use source(). Have your R code in one buffer, and
the R session running, and (from the code buffer), type C-c C-l.
Cheers
Jason
__
Uwe Ligges <[EMAIL PROTECTED]> writes:
> Webb Sprague wrote:
>>
>> Hi all,
>>
>> I have searched but to know avail. Is there a way to get a line number
>> when a function crashes? I am doing an edit->source->run cycle.
>
> I don't think so, but traceback(), debug() and options(error = recover)
Hi Patrick,
It's very simple using a browser() line in your function somewhere you
know your code's OK, then run line by line.
The problem is that sometimes you have code of a few hundred lines, to
which you have added a strange little line that craps out because of
some silly mistake that wo
Webb Sprague wrote:
>
> Hi all,
>
> I have searched but to know avail. Is there a way to get a line number
> when a function crashes? I am doing an edit->source->run cycle.
I don't think so, but traceback(), debug() and options(error = recover)
are your friends.
Also, you might want to check
Hi all,
I have searched but to know avail. Is there a way to get a line number
when a function crashes? I am doing an edit->source->run cycle.
Feel free to cc me as I subscribe to the list in digest.
Thanks
W
__
[EMAIL PROTECTED] mailing list
https:
17 matches
Mail list logo
