[R] Tinn-R not working well with latest R
Philippe Grosjean
phgrosjean at sciviews.org
Thu Feb 14 14:47:40 CET 2008
Hello,
These are *warnings*. So, the functions should still work. However,
there are changes made in R that probably need some lifting in the svIDE
package. The whole SciViews bundle is currently reworked.
Unfortunately, I now work on Mac OS X, and it is a little bit more
difficult for me to test this with Tinn-R. Could you give me more infos
about the "great features in Tinn-R" that stop working in R 2.6.2, please?
Best,
Philippe Grosjean
..............................................<°}))><........
) ) ) ) )
( ( ( ( ( Prof. Philippe Grosjean
) ) ) ) )
( ( ( ( ( Numerical Ecology of Aquatic Systems
) ) ) ) ) Mons-Hainaut University, Belgium
( ( ( ( (
..............................................................
Farrel Buchinsky wrote:
> I recently installed R 2.6.2 and am getting errors on startup that
> relate to svIDE being loaded by Tinn-R.
>
>
> Loading required package: tcltk
> Loading Tcl/Tk interface ... done
> Warning messages:
> 1: '\A' is an unrecognized escape in a character string
> 2: unrecognized escape removed from ";for Options\AutoIndent: 0=Off,
> 1=follow language scoping and 2=copy from previous line\n"
> 3: In grep(paste("[{]TclEval ", topic, "[}]", sep = ""),
> tclvalue(.Tcl("dde services TclEval {}")), :
> argument 'useBytes = TRUE' will be ignored
> Loading required package: svMisc
> Loading required package: R2HTML
>
>
> Any idea what is going on.
> I use R 2.6.2 on windows xp
>
> I also started R without the profile that Tinn-R made.
> If I manualy enter library(svIDE) then I get.
> > library(svIDE)
> Warning messages:
> 1: '\A' is an unrecognized escape in a character string
> 2: unrecognized escape removed from ";for Options\AutoIndent: 0=Off,
> 1=follow language scoping and 2=copy from previous line\n"
>
> So the underlying problem may be svIDE
> see: http://tolstoy.newcastle.edu.au/R/e2/help/07/04/15738.html
>
> Apparently, because of this error, several great features in Tinn-R are
> not working properly.
> Any solutions or workarounds?
>
>
> --
> Farrel
More information about the R-help
mailing list