similar to: Fwd: Re: Problem running RTERM via SSH on Windows/2000

I'm having problems getting RTERM to work via SSH. Whenever it has any type of problem, it abends instead of issuing an error message and returning to the > prompt. Both "server" and client are Windows/2000 Professional at FP4. SSH is via Cygwin on both sides. R is version is 1071. RTERM runs fine when run in a BASH shell on the "server," though it does not prompt

I've been having problems with Rterm.exe not shutting down when I exit an R (1.7.0 and 1.7.1) session from within emacs when using ESS. I've just upgraded to 5.1.24 and still have the same problems. I'm running ntemacs and winxp. I don't recall having these troubles with version 1.6.2 of R. Jeff. --- Jeff D. Hamann Hamann, Donald and Associates, Inc. PO Box 1421 Corvallis, Oregon

Hi to all who suffer from rterm not shutting down in xemacs/ESS on windows NT or 2000. Also hi to those who could eventually help. Here is some more information which could help and some ENCOURAGEMENT to contribute to a solution. 1. It may be an xemacs problem but it is more likely an interaction between rterm/comint/and xemacs. In fact, the problem started occurring around version R 1.6.0. I

The following becomes more and more a topic for an R mailing list, possibly R-devel. R for Windows crashes are important and should be discussed and debugged with the experts -- which are not reading ESS-help AFAIK. Martin >>>>> "ColCun" == Cunningham, Colin A <colin.a.cunningham@intel.com> writes: ColCun> In my very brief exposure to R, I have

> From: rossini@biostat.washington.edu (A.J. Rossini) > Date: 23 Nov 1998 12:46:03 -0800 > > Thanks much. I'm hacking Emacs/ESS on MS Windows platforms starting > mid next month, thanks to some external prodding (and now, product > availability from both R, Splus). And I think XLispStat might be able > to talk (at least DDE), as well, which would be nice > > If

Guido has fixed Rterm hanging on Windows 2000 in interactive and --ess modes. The problem was that 'PulseEvent' doesn't work under 2000 as documented (and I can find nothing about this in MicroSoft's Knowledge Base except that it is known to happen under a debugger). The cross-compiled pre-release at http://www.stats.ox.ac.uk/pub/bdr/RWin/Rpre now incoporates the fix, and we

I think the message from Prof. Ripley refers to calling shell and system from R. There is no "system" call in Windows cmd or VBA and I am calling R from VBA. Now I want to use tryCatch to output the error to a text file and exit gracefully. My expression will be source("file.r") and that will contain file I/O and db connect+query. to exemplify I am trying with

SVN revision replaces "slave" with "no-echo" in R devel. In each of the following, "no-echo" is rather strange to me. - src/gnuwin32/README.Rterm 3) As a no-echo process for ESS mode in NTEmacs with flag --ess. - src/library/grDevices/src/qdCocoa.m /* the no-echo thread work until this is NO */

I am running R.exe/Rterm.exe 2.7.1 under Emacs 22.1 under the DOS shell under Windows XP. (My Cygwin installation is broken!) I am not currently using ESS: > R.exe --vanilla R version 2.7.1 ... ... > 1+1 2 This works fine until I hit an R error -- pretty much any error -- when the process halts and returns to the shell: Wrong number of arguments error: > quote()

I've just installed R 1.1.0 under Windows 2000 in a Pentium Mobile III 600MHh. Everything seems to work fine except Rterm. Rterm runs but only accepts one command, it doesn't return the R promt. This is a problem to run R under Emacs and in a "BATCH" mode. Is there a workaround or a solution to this problem. Please reply directly to me, in summer I'm not subscribed to the

A new version of R for Windows is available from CRAN in directory bin/windows/windows-NT. This supersedes rw0630, rw63-io, bdr0631 and earlier versions. It runs on Windows 95, 98, NT4 (on i386), at least. There are two executables, Rgui.exe and Rterm.exe. NEW FEATURES Will run from NT command line. No `tricks' are needed for animated graphics. The windows are much more responsive.

A new version of R for Windows is available from CRAN in directory bin/windows/windows-NT. This supersedes rw0630, rw63-io, bdr0631 and earlier versions. It runs on Windows 95, 98, NT4 (on i386), at least. There are two executables, Rgui.exe and Rterm.exe. NEW FEATURES Will run from NT command line. No `tricks' are needed for animated graphics. The windows are much more responsive.

The first of Suharno's examples can be viewed that way, because R under ESS is not a "slave" in the technical sense, just a situation where you do not want keyboard input to be echoed. "Non-echoing" might have been better language though. The 2nd example really is of the master/slave variety, and to my knowledge nothing to do with echoing, so looks like a

I have used S-PLUS for years. Now I am learning to use R in Windows'98. I downloaded the latest version and installed it as instructed. However, I cannot find answers from online help to the following questions I encountered. If any of you has quick answers to these questions, please drop me a couple of lines. Thanks. 1. Why does R change my working directory during a session? I often used

Colleagues, I have encountered the following situation in R (2.9.0) with Windows XP. I have an application that calls Rterm.exe. In certain situations, the application terminates but fails to close R. Then, the next time that the application runs, there are replicated copies of R running - this slows the system. One solution would be to kill any open versions of Rterm.exe each time

FYI, via a bug report of one of my packages, I discovered that the following cases will hang Rterm when using TAB completion: CASE #1: Adding an empty default function for tail() causes Rterm on Windows to hang if one press TAB at the prompt: % Rterm -vanilla > tail.default <- function(...) {} > [PRESS TAB] Error in specialOpLocs(text) : (list) object cannot be coerced to type

Dear R users, Does anyone notice that Rterm.exe does not work well with rxvt.exe, an xterm emulator for Cygwin? It produces an error message window with the following message: This program has performed an illegal operation and will be shut down. If the problem persists, contact the program vendor It also prints "Signal 127" in rxvt window. Rterm --ess, however, works.

Yes, indeed, I am talking about Rterm in Windows. Iago ________________________________ De: Duncan Murdoch <murdoch.duncan at gmail.com> Enviat el: divendres, 9 de febrer de 2024 13:50 Per a: Iago Gin? V?zquez <iago.gine at sjd.es> Tema: Re: [R] Avoiding Delete key function as 'Quit R' in Rterm when there are no characters in cursor line On 09/02/2024 6:25 a.m., Iago Gin?

I would like to use R as the graphical interface for a fortran program I am writing. Presently my fortran code produces a set of data files then sends an "rterm ..... <filename.r >out.out" line to my windows system. This causes rterm to read in the data files, draw plots on my screen in milliseconds .... and then terminate and disappear, plots and all, forever. It's this last

That looks to me like a bug, but I don't use Windows any more, so I won't offer to try to fix it for you. In fact I don't think Rterm has many users at all: most Windows users probably use RStudio or one of the other graphical front ends (Visual Studio, Emacs, Rgui, etc.) So maybe you can track down the issue, or someone else will try. Or maybe you'll just have to avoid