search for: swinregistri

Hi all, I am trying to install add-on in R (rw1070) to work with WinEdit. Libraries Swinregistry and Rwinedt have been installed via "Install Package(s) from local zip files" from R. However, when I run library(Rwinedt) I get the following messages: > library(Rwinedt) Loading required package: SWinRegistry Error in loadNamespace(name) : package `methods' does not have a name

Hi I have R 1.6.2 and use WinEdt as a text editor. I have just upgraded to R 1.8.0 but can't set up the SWinRegistry program. Using the recommended "Install packages from local zip files" menu option I get > install.packages("C:/R/SWinRegistry_0.3-2_binary.zip", .libPaths()[1], CRAN = NULL) Error in file(file, "r") : unable to open connection In addition:

Hi: I just tried to install the patch for RWinEdt - there is an automated package ('SWinRegistry' ) which with the rwinedt patch on the CRAN site have to be loaded as packages from R using the local zip drive option. That works fine. The next step is to call the library(RwinEdt) and this does'nt work out ... the meesages i get are: >

Buenas tardes a todos: Primero que nada un saludo y desearles un feliz 2009. Escribo para que me asesoren con la instalación de un editor de R, estube siguiendo los pasos de un manual 1. Instalar R 2. Instalar WinEdt 5 (V. 5.2 o superior) 3. Instalar *SWinRegistry *(disponible en http://www.omegahat.org/SWinRegistry): *Packages ! Install package(s) from local zip ¯les... * 4. Instalar

There was a user request to announce this new version (1.6-0) of R-WinEdt (actually, the request was to announce version 1.5-1). It is propagating through CRAN these days and (is|will be) available at yourCRANmirror/contrib/extra/winedt/ For those who have not already noticed the changes since R-WinEdt 1.4-x, I'd like to summarize the changes below. The most exciting one is the new

I am attempting to use R through WinEdt. I installed the SWinRegistry package and it seems to install fine. But when I type: > library(RWinEdt) I get: Error in library(WinEdt) : there is no package called 'RWinEdt' I am running Windows XP and R 1.8.1 The SWinRegistry is correctly named as well that is it is named: SWinRegistry_0.3-3.zip, which I know caused

Hi, I have just upgraded from the 1.8.1 to the 1.9.0 version of R, and have some trouble to run RWinEdt from the .Rprofile file (in the user folder). The script is: library(MASS) library(lattice) cat("Load editor?(y/n default = y): ") nf <- as.character(readLines(n = 1)) if ((nf=="y")|(nf=="Y")|(nf=="")) {library(RWinEdt)} rm(nf) When run at start,

Good morning and good year :D Thanks so much, I did what you told me (that actually was the same I was doing but wit a previus version of R and WinEdt) and it worked out well. Thank's again. On Thu, Jan 1, 2009 at 8:28 AM, Uwe Ligges <ligges@statistik.tu-dortmund.de>wrote: > Well, I really cannot understand everything in your message, but I hope I > got the essential points:

Hi, I have troubles getting RWinEdt with the R2.0.0 Version startet. Do I have to install a different version of RWinEdt or WinEdt? I have RWinEdt 1.6.1 and WinEdt 5.3. Thanks Anna Hennig

I have finally got around to putting 4 packages on the Omegahat web site for use on Microsoft Windows. The packages are: RDCOMClient - interactive, dynamic access to arbitrary (D)COM objects from within R that allows one to create COM objects from R and call their methods and access their properties without the need to compile any code specific to the COM object. RDCOMServer - facility for

Hello all Can R be used as a COM client (rather than as a COM server)? The following (Splus) code shows the sort of thing I'd like to do: pMIM <- create.ole.object("mim31.Server") NoOutputLines <- call.ole.method(pMIM, "SendCmdLine", "show w") for (i in 1:NoOutputLines) show(call.ole.method(pMIM, "GetOutputLine")) release.ole.object(pMIM)

I implemented Uwe's R-WinEdt package as a closer to true WinEdt mode so that WinEdt could be used with other modes as well. I sent Uwe the implementation and we talked a little about cleaning it up, but I haven't gotten around to it and I don't think he has either. It is still a little messy as Uwe noted below but it works well. There is no code changes, just running a WinEdt macro