On Wed, 2007-06-13 at 08:04 -0700, Seth Falcon wrote:
> Jari Oksanen <[EMAIL PROTECTED]> writes:
>
> > On Wed, 2007-06-13 at 13:33 +0100, Gavin Simpson wrote:
> >> Dear Developers,
> >>
> >> This change also just bit me whilst updating Sweave documents for some
> >> computer classes.
> >>
> >> I
Jari Oksanen <[EMAIL PROTECTED]> writes:
> On Wed, 2007-06-13 at 13:33 +0100, Gavin Simpson wrote:
>> Dear Developers,
>>
>> This change also just bit me whilst updating Sweave documents for some
>> computer classes.
>>
>> Is there a work-around that can be employed so that we get both the
>> me
> On Wed, 13 Jun 2007 16:43:32 +0300,
> Jari Oksanen (JO) wrote:
> On Wed, 2007-06-13 at 13:33 +0100, Gavin Simpson wrote:
>> Dear Developers,
>>
>> This change also just bit me whilst updating Sweave documents for some
>> computer classes.
>>
>> Is there a work-around that
On Wed, 2007-06-13 at 13:33 +0100, Gavin Simpson wrote:
> Dear Developers,
>
> This change also just bit me whilst updating Sweave documents for some
> computer classes.
>
> Is there a work-around that can be employed so that we get both the
> message() bits and the print() bits in the same place
Dear Developers,
This change also just bit me whilst updating Sweave documents for some
computer classes.
Is there a work-around that can be employed so that we get both the
message() bits and the print() bits in the same place for our Sweave
files?
If not, is there any point in filing this as a
Dear developers,
I just noticed that step() function currently prints the current model
using message(), but the resulting model using print(). The relevant
commands within the step() body are:
if (trace) message("Start: AIC=", format(round(bAIC, 2)), "\n",
cut.string(deparse(as.vector(form
