similar to: rterm 1.1.1 under windows 2000

Hello Users: I'm using R version 2.0.1, and having problems with RODBC. Everything works fine when I use Rgui, but when I try to use Rterm and issue the commands library(RODBC) con <- odbcConnect("MySQL", "test") I get the following error: Error in sqlQuery(con, str) : first argument is not an open RODBC channel In addition: Warning messages:

Dear developers, I have come across a (somewhat strange) change in the encoding of Sweave output from R-2.9.2pat to R-2.10.0beta (apparently specific to Rgui) on Windows installations. Of course, the NEWS file contains quite a few changes concerning encoding, but I was not able to locate an entry which explains the observed behaviour. I am not very familiar with encodings/locales/codepages,

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

I'm running an R script in Rterm and would like the user to be prompted for input as in: id <- readline("Please enter ID: ") myfunction(id) . . . etc. This works when I run one line at a time in RGui, but not when I try to run the script in Rterm (I'm working with R 2.2.0 in Windows Server 2003). Is there any way to do this? Mikkel

Hello everyone, I am new to R and I have experienced some bugs when using Rterm on Windows. Chinese characters in the console output are discarded by Rterm, and trying to type them into the console will crash the Rterm application. ---ENVIRONMENT--- Platform = x86_64-w64-mingw32 OS = Windows 10 Pro 1709 chs R version = 3.4.3 Active code page = 936 (Simplified Chinese) ---STEPS TO

Hello. I am trying to build R on Windows. It appears that my build passes the various "make checks" (unless I missed some error) and running Rterm seems to work fine whereas Rgui has an immediate error stating " AppName: rgui.exe AppVer: 2.150.58871.0 ModName: rzlib.dll ModVer: 0.0.0.0 Offset: 0000a9e5 The taskbar still works, but the console window has nothing in it, and

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.

Since R0633 I have noticed when typing fast inside the dos window of the Rterm, R did not pickup correctly, If I type () fast, it shows as )). I am using windows NT 4.0 R0640, and click on the Rterm to pop up a dos window with R. I was wondering if it is my typing, but the same typing do not show error inside the Rgui window. Mai Z

I've been trying to use Rterm.exe, mainly because of Rgui.exe's lack of support for incremental history searching. But on my system (Win XP, SP3), it (rterm from R-2.8.1) frequently just stops responding to keyboard input. This happens often (enough to make it unusable), and generally after a switch to another window. It doesn't seem to hang exactly, as if I leave it a while (minutes)

[Environment: Win XP, R 2.10.1] In my Rprofile I have startup code to do various things, intended for when I use the Rgui console. Some of these are causing problems in JGR now that I've installed it. How can I test for R running with Rgui to do some of these things only there? -- Michael Friendly Email: friendly AT yorku DOT ca Professor, Psychology Dept. York University

Hi Tomas, Sorry for the delayed response. I have tested the problem on the latest R-devel build (2018-04-27 r74651), and it still exists. RGui is always fine with Chinese characters, but some IDEs rely on the CLI version of R (e.g. Visual Studio Code with R plugin). >Your example print("ABC\u4f60\u597dDEF") is printing two Chinese characters, right? Yes. U+4F60, U+597D or C4E3,

I have downloaded rw0632 (Windows Version) from the CRAN at ETH Zuerich. Im working with NT4.0 Service Pack 4. I can start without any problems the GUI program Rgui.exe. But by using Rterm.exe (batch mode or with ESS respectivelly) I always get an error "the instruction at "0x10018ee8" referenced memory at ""......." Any ideas what is wrong? Best Regards Markus

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

Dear list, I?m using R embedded in another program (coded in tcl/tk) under Windows Vista. In this context I don?t launch Rgui.exe but rather Rtem.exe. Now I have a problem finding libraries not specifically installed as administrator (and which are not in the path ?program files? but in Contacts\Documents of the current user). To be precise, the user launching my tcl/tk program can?t find

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?

Greetings, I am trying to run a short script from a shell: c:\projects\hell>Rscript --default-packages=mypack X:/4Stephen/commit/curve.R > X:/4Stephen/commit/run1.out Loading required package: utils Warning message: package 'RODBC' was built under R version 2.12.2 Error: could not find function "normalize" Execution halted Warning message: closing unused RODBC handle 1

I don't use term, but I've just tested it and this is reproducable. Is it a bug? Not sure. If you hit c after getting the message it will cancel the q() request. On Fri, 9 Feb 2024, 17:21 Duncan Murdoch, <murdoch.duncan at gmail.com> wrote: > 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

Hi all, I have just installed R 2.13.0 and I am experiencing problems with the terminal, but not the with the GUI interface. I am Windows 7. When running "R" or "Rterm" from a commandline I receive the following: Warning message: In normalizePath(path.expand(path), winslash, mustWork) : path[3]="C:/Programmer/R/R-2.13.0/library": Adgang n?gtet R version 2.13.0

For processing events, RGtk2 has moved away from using the old tcl_do hack and now synchronizes on the Windows event loop. In Rgui.exe this works fine (well mostly), but in Rterm.exe, users report the following warning from GLib: "main loop already active in another thread". The most obvious way this could occur is if the Windows event loop were iterating in multiple threads. This does

minimal reproducible example plot(1,1) identify(1,1) # or locator() now, trying to close the window by clicking on the cross of the upper right corner causes Rgui (and Rterm) to crash. I see the same behaviour on 2 different Windows PC (one with Win 8.1 and one with Win 10). I did not see the problem in linux (see below) WINDOWS ************** > sessionInfo() R version 3.3.0 beta