# Your mailer is set to "none" (default on Windows), # hence we cannot send the bug report directly from R. # Please copy the bug report (after finishing it) to # your favorite email program and send it to # # r-bugs@r-project.org # ###################################################### <<insert bug report here>> There are two bugs associated with graphics devices. One new, one old. 1. The new one. When I include trellis.device() in my .First, Rterm 1.8.1 run in ESS happily opens a device. Rterm 1.9.0 doesn't. It gives the following message instead:> [Previously saved workspace restored] > > Error in get(x, envir, mode, inherits) : variable "windows" was not found2. The old one. When no device has been opened, then q() cleanly closes R. When a graphics device has been opened, and either is still open or was manually closed, then q() hangs. I need to kill it from the Windows Task Manager. Rich --please do not edit the information below-- Version: platform = i386-pc-mingw32 arch = i386 os = mingw32 system = i386, mingw32 status = major = 1 minor = 9.0 year = 2004 month = 04 day = 12 language = R Windows XP Home Edition (build 2600) Service Pack 1.0 Search Path: .GlobalEnv, package:methods, package:stats, package:graphics, package:utils, file:c:/HOME/rmh/hh/splus.library/HH/.RData, package:lattice, package:grid, Autoloads, package:base
On Fri, Apr 23, 2004 at 01:29:18AM +0200, rmh@temple.edu wrote:> 2. The old one. > > When no device has been opened, then q() cleanly closes R. > When a graphics device has been opened, and either is still open or was > manually closed, then q() hangs. I need to kill it from the Windows Task > Manager.Hm, I don't think I've ever seen that under NT4 or win2k at work. I use Rterm in ESS as well as Rgui, and close it frequently with open graphics devices. Could that have something to do with your particular graphics card, or with XP home? What windows variants do you use? Dirk -- The relationship between the computed price and reality is as yet unknown. -- From the pac(8) manual page
On Fri, 23 Apr 2004 01:29:18 +0200 (CEST), rmh@temple.edu wrote:>1. The new one. > >When I include > trellis.device() >in my .First, Rterm 1.8.1 run in ESS happily opens a device. > >Rterm 1.9.0 doesn't. It gives the following message instead: > >> [Previously saved workspace restored] >> >> Error in get(x, envir, mode, inherits) : variable "windows" was not foundSounds like lattice needs to import windows. (In 1.8.1 windows() was in base, so it would have automatically been available in .First.)>2. The old one. > >When no device has been opened, then q() cleanly closes R. >When a graphics device has been opened, and either is still open or was >manually closed, then q() hangs. I need to kill it from the Windows Task >Manager.I don't see this. Which device? Does it happen if if you start R with the --vanilla option? Duncan Murdoch
> From: dmurdoch@pair.com > > On Fri, 23 Apr 2004 01:29:18 +0200 (CEST), rmh@temple.edu wrote: > > >2. The old one. > > > >When no device has been opened, then q() cleanly closes R. > >When a graphics device has been opened, and either is still > open or was > >manually closed, then q() hangs. I need to kill it from the > Windows Task > >Manager. > > I don't see this. Which device? Does it happen if if you start R > with the --vanilla option? > > Duncan MurdochI have not had the problem until we got `upgraded' from NT4 to XPPro. (It's the windows() device. I have not tested others.) As Rich said, it's an old one, and apparently doesn't happen to everyone. It was one of the reasons I only use ESS basically for editing code, not for running R. Best, Andy ------------------------------------------------------------------------------ Notice: This e-mail message, together with any attachments,...{{dropped}}
This is a start of R 1.9.0 in a directory without .RData> options(STERM='iESS', editor='gnuclient.exe') > search()[1] ".GlobalEnv" "package:methods" "package:stats" "package:graphics" [5] "package:utils" "Autoloads" "package:base"> find(windows)[1] "package:graphics">This makes me think that the .First is being processed before some of the other initializations. I had been assuming it is the very last thing done before it gives me control. This introduces a new problem---both 1.9.0 and 1.8.1. I did --vanilla as you suggested, in a directory without an existing .RData /cygdrive/c/HOME/tmp$ Rterm --vanilla R : Copyright 2004, The R Foundation for Statistical Computing Version 1.9.0 (2004-04-12), ISBN 3-900051-00-3 R is free software and comes with ABSOLUTELY NO WARRANTY. You are welcome to redistribute it under certain conditions. Type 'license()' or 'licence()' for distribution details. R is a collaborative project with many contributors. Type 'contributors()' for more information and 'citation()' on how to cite R in publications. Type 'demo()' for some demos, 'help()' for on-line help, or 'help.start()' for a HTML browser interface to help. Type 'q()' to quit R.> date()date() [1] "Thu Apr 22 21:52:14 2004"> ls()ls() character(0)> nonsensenonsense Error: Object "nonsense" not found Execution halted /cygdrive/c/HOME/tmp$ When I manually start the trellis.device, after a version of my .First that doesn't start it for me, I get this> .Device[1] "windows">on the q() issue, I report it as a continuation of behavior that has been discussed on this list. I don't remember when. It has been an issue for me for a long time. I am currently on XP HOME, I see this also on NT4. I normally type just q() This time I tried q("no"). It still freezes. I have to enter C-G to unfreeze emacs and then use the Task Manager to kill the Rterm process. Rich
On Thursday 22 April 2004 19:31, Duncan Murdoch wrote:> On Fri, 23 Apr 2004 01:29:18 +0200 (CEST), rmh@temple.edu wrote: > >1. The new one. > > > >When I include > > trellis.device() > >in my .First, Rterm 1.8.1 run in ESS happily opens a device. > > > >Rterm 1.9.0 doesn't. It gives the following message instead: > >> [Previously saved workspace restored] > >> > >> Error in get(x, envir, mode, inherits) : variable "windows" was > >> not found > > Sounds like lattice needs to import windows. (In 1.8.1 windows() was > in base, so it would have automatically been available in .First.)How do I do that ? windows is not available in all platforms, and on the one I use, importFrom(graphics, windows) leads to (during R INSTALL): Error in importIntoEnv(impenv, impnames, ns, impvars) : object(s) 'windows' are not exported by 'namespace;graphics' Is Rich's usage valid under 1.9.0 ? I presume replacing trellis.device() by windows() will give the same error. Or are all lattice functions expected to work after a require(lattice) is included in .First ? Deepayan
On Thu, 22 Apr 2004 22:08:56 -0400, "Richard M. Heiberger" <rmh@temple.edu> wrote:>This is a start of R 1.9.0 in a directory without .RData > > >> options(STERM='iESS', editor='gnuclient.exe') >> search() >[1] ".GlobalEnv" "package:methods" "package:stats" "package:graphics" >[5] "package:utils" "Autoloads" "package:base" >> find(windows) >[1] "package:graphics" >> > > >This makes me think that the .First is being processed before some of the other >initializations. I had been assuming it is the very last thing done before it gives me >control.Yes, see ?Startup for the details. I think the startup sequence hasn't changed in 1.9.0 (though the documentation for it is now more accurate), but the rearrangement of packages means that things that worked before in .First won't work now.>on the q() issue, I report it as a continuation of behavior that has been discussed >on this list. I don't remember when. It has been an issue for me for a long time. >I am currently on XP HOME, I see this also on NT4. > >I normally type just q() >This time I tried q("no"). > >It still freezes. I have to enter C-G to unfreeze emacs and then use the Task Manager >to kill the Rterm process.Sorry, didn't notice the earlier discussion. Sounds like an interaction with ESS. Which Emacs are you using (and perhaps, where can I get it? I have XEmacs installed on one machine, but not this one). Duncan Murdoch