8 messages · Jari Oksanen, Jonathan Baron, Martyn Plummer +3 more
The RPM for Fedora Core 2 seems to work just fine on Core 3. (The graphics window got smaller, but I'm sure there is a setting for that.) Jon
Jonathan Baron, Professor of Psychology, University of Pennsylvania Home page: http://www.sas.upenn.edu/~baron R search page: http://finzi.psych.upenn.edu/
The RPM for Fedora Core 2 seems to work just fine on Core 3. (The graphics window got smaller, but I'm sure there is a setting for that.)
That would be good news. I really don't know how the graphics window became so big at some stage. (MacOS X is just cute here: tiny, sharp, fast graphics window.) Has the options()printcmd reappeared, so that dev.print() works without changing default options? cheers, jazza -- Jari Oksanen, Oulu, Finland
On 9 Nov 2004, at 19:44, Jonathan Baron wrote:
The RPM for Fedora Core 2 seems to work just fine on Core 3. (The graphics window got smaller, but I'm sure there is a setting for that.)
That would be good news. I really don't know how the graphics window became so big at some stage. (MacOS X is just cute here: tiny, sharp, fast graphics window.)
I have the opposite problem, a 1680x1050 display.
Has the options()printcmd reappeared, so that dev.print() works without changing default options?
I can't imagine how this would change. This is the same "old" RPM, not a new one. The option is there, and I don't think it ever disappeared. I can't test it. This is my laptop, which is not set up to print anything. Jon
Jonathan Baron, Professor of Psychology, University of Pennsylvania Home page: http://www.sas.upenn.edu/~baron
On 11/09/04 20:37, Jari Oksanen wrote:
On 9 Nov 2004, at 19:44, Jonathan Baron wrote:
The RPM for Fedora Core 2 seems to work just fine on Core 3. (The graphics window got smaller, but I'm sure there is a setting for that.)
That would be good news. I really don't know how the graphics window became so big at some stage. (MacOS X is just cute here: tiny, sharp, fast graphics window.)
I have the opposite problem, a 1680x1050 display.
Has the options()printcmd reappeared, so that dev.print() works without changing default options?
I can't imagine how this would change. This is the same "old" RPM, not a new one. The option is there, and I don't think it ever disappeared. I can't test it. This is my laptop, which is not set up to print anything.
My mistake. The default print command is determined at configure time. But the RedHat RPMS are built in a sandbox that has only the minimal configuration needed to build R. This doesn't include the lpr package so the default print command is null. I will fix this in the next RPM release, but right now I am upgrading to FC3. Martyn
On Tue, 2004-11-09 at 19:47, Jonathan Baron wrote:
On 11/09/04 20:37, Jari Oksanen wrote:
On 9 Nov 2004, at 19:44, Jonathan Baron wrote:
The RPM for Fedora Core 2 seems to work just fine on Core 3. (The graphics window got smaller, but I'm sure there is a setting for that.)
That would be good news. I really don't know how the graphics window became so big at some stage. (MacOS X is just cute here: tiny, sharp, fast graphics window.)
I have the opposite problem, a 1680x1050 display.
Has the options()printcmd reappeared, so that dev.print() works without changing default options?
I can't imagine how this would change. This is the same "old" RPM, not a new one. The option is there, and I don't think it ever disappeared. I can't test it. This is my laptop, which is not set up to print anything.
My mistake. The default print command is determined at configure time. But the RedHat RPMS are built in a sandbox that has only the minimal configuration needed to build R. This doesn't include the lpr package so the default print command is null. I will fix this in the next RPM release, but right now I am upgrading to FC3.
An RPM for Fedora Core 3 should be on a CRAN mirror near you by the weekend. This fixes the printcmd bug. The X11() window is the right size for me, but it doesn't have a title bar, which is a nuisance. Martyn
On Wed, 2004-11-10 at 09:19 +0100, Martyn Plummer wrote:
<snip>
An RPM for Fedora Core 3 should be on a CRAN mirror near you by the weekend. This fixes the printcmd bug. The X11() window is the right size for me, but it doesn't have a title bar, which is a nuisance. Martyn
I have this "problem" with both your rpm on FC2 and when compiled from sources (1.9.1-patched 2.0.0-patched [now 2.0.1 beta]). The title bar comes and goes, seemingly at random (I've not systematically test this so I haven't found an underlying cause) when a new X11() device is started. Mainly a more complex plot (over several lines and commands) will fail to produce the title bar, if I then close that device and open another using something simple, say plot(1:10) then I more often than not get the title bar. I say more often than not, because sometimes I have to run that command a few times, closing the opened faulty device window in between to get the title bar to appear. Same result running R from within xemacs/ess. Gav
%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~% Gavin Simpson [T] +44 (0)20 7679 5522 ENSIS Research Fellow [F] +44 (0)20 7679 7565 ENSIS Ltd. & ECRC [E] gavin.simpson at ucl.ac.uk UCL Department of Geography [W] http://www.ucl.ac.uk/~ucfagls/cv/ 26 Bedford Way [W] http://www.ucl.ac.uk/~ucfagls/ London. WC1H 0AP. %~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%~%
I've run into this title bar problem on FC1 and FC2 (not tried FC3 yet) when I compile from sources. I figured it was just a weird window manager bug. I find that if I maximize the window (Alt-F10, on my system) and then restore the window to its original size (Alt-F5), I get the title bar back. -roger
Martyn Plummer wrote:
On Wed, 2004-11-10 at 09:19 +0100, Martyn Plummer wrote:
<snip>
An RPM for Fedora Core 3 should be on a CRAN mirror near you by the weekend. This fixes the printcmd bug. The X11() window is the right size for me, but it doesn't have a title bar, which is a nuisance. Martyn
I have this "problem" with both your rpm on FC2 and when compiled from sources (1.9.1-patched 2.0.0-patched [now 2.0.1 beta]). The title bar comes and goes, seemingly at random (I've not systematically test this so I haven't found an underlying cause) when a new X11() device is started. Mainly a more complex plot (over several lines and commands) will fail to produce the title bar, if I then close that device and open another using something simple, say plot(1:10) then I more often than not get the title bar. I say more often than not, because sometimes I have to run that command a few times, closing the opened faulty device window in between to get the title bar to appear. Same result running R from within xemacs/ess. Gav
Roger D. Peng http://www.biostat.jhsph.edu/~rpeng/
On Wed, 2004-11-10 at 09:19 +0100, Martyn Plummer wrote:
On Tue, 2004-11-09 at 19:47, Jonathan Baron wrote:
On 11/09/04 20:37, Jari Oksanen wrote:
On 9 Nov 2004, at 19:44, Jonathan Baron wrote:
The RPM for Fedora Core 2 seems to work just fine on Core 3. (The graphics window got smaller, but I'm sure there is a setting for that.)
That would be good news. I really don't know how the graphics window became so big at some stage. (MacOS X is just cute here: tiny, sharp, fast graphics window.)
I have the opposite problem, a 1680x1050 display.
Has the options()printcmd reappeared, so that dev.print() works without changing default options?
I can't imagine how this would change. This is the same "old" RPM, not a new one. The option is there, and I don't think it ever disappeared. I can't test it. This is my laptop, which is not set up to print anything.
My mistake. The default print command is determined at configure time. But the RedHat RPMS are built in a sandbox that has only the minimal configuration needed to build R. This doesn't include the lpr package so the default print command is null. I will fix this in the next RPM release, but right now I am upgrading to FC3.
An RPM for Fedora Core 3 should be on a CRAN mirror near you by the weekend. This fixes the printcmd bug. The X11() window is the right size for me, but it doesn't have a title bar, which is a nuisance. Martyn
I've seen this with X11 a little on FC2 but much more with rgl (maybe 50% of the time with rgl vs 5-10% for X11()). Ross Ihaka tried replacing the default metacity window manager with sawfish and found that the problem seemed to go away. Ross also found a bug report for metacity, https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=126571 that might be related. It might also be something we are not doing quite right in opening a window that happens to bite metacity more than other wms. If anyone has the time and energy to pursue this please do. Best, luke
Luke Tierney University of Iowa Phone: 319-335-3386 Department of Statistics and Fax: 319-335-3017 Actuarial Science 241 Schaeffer Hall email: luke at stat.uiowa.edu Iowa City, IA 52242 WWW: http://www.stat.uiowa.edu